Two teams finish the group stage on six points each. One walks into the semi-final, the other flies home, and the only thing separating them is a number in the last column of the table. That number is net run rate, and if you have ever watched a captain send his openers out to swing at everything with the match already won, this is the reason.
It is the standard tiebreaker in almost every limited-overs tournament — World Cups, the PSL, domestic one-day cups. It rewards teams that win big and punishes teams that scrape home. The idea is simple. Two of the rules around it are not, and those two decide qualification more often than most viewers realise.
What net run rate actually measures
Strip out the jargon and you are comparing two speeds: how fast you scored, and how fast the opposition scored against you.
The formula, as set out by Olympics.com, is your total runs divided by your total overs faced, minus the total runs scored against you divided by the total overs you bowled. A positive figure means you have generally outscored your opponents across the tournament. A negative figure means the opposite.
That is the whole concept. Everything else is bookkeeping — but the bookkeeping is where teams win and lose places.
One note on the arithmetic first. Overs are written as 17.2, meaning seventeen overs and two balls. You cannot type 17.2 into a calculator here. Two balls is a third of an over, so 17.2 overs is 17.33. Getting that wrong is the most common mistake when readers try the maths themselves.
A worked example you can follow
Take a T20 match. Team A bats first and makes 168 in its full 20 overs. Team B chases 169 and gets there in 17.2 overs.
Team B scored 169 off 17.33 overs, which is 9.75 runs per over. It conceded 168 off 20 overs, which is 8.40. Team B’s net run rate from that match is 9.75 minus 8.40, or +1.35. Team A’s is the mirror image: −1.35.
Now change one thing. Suppose Team B had chased the same target in 16 overs instead. Its scoring rate becomes 169 divided by 16, or 10.56, and its match figure jumps to +2.16. Twenty balls saved is worth eight tenths of a point. That is why a side already 40 runs clear of the target still takes risks in the fifteenth over.
Getting bowled out is the expensive part
Here is the rule that surprises people. If a team is dismissed before it has used its full allocation, the calculation still divides its runs by the full quota of overs — not by the overs it actually faced.
Go back to Team B, but this time it collapses for 120 in 15.4 overs. You might expect its scoring rate to be 120 divided by 15.67, which is 7.66. It is not. Because the side was bowled out, the runs are divided by all 20 overs: 6.00. The same 120 runs, and the rate drops by more than a run and a half per over.
The reason is obvious once you see it. Without the rule, a team could throw wickets away in a lost cause, finish quickly, and keep its rate looking respectable.
There is a matching effect at the other end. Team A, having bowled the opposition out for 120, has those runs counted against it over the full 20 overs too — so its conceded rate is 6.00 and its match figure becomes +2.40. Bowling a side out is worth real points in the standings.
Why the tournament figure is not an average
This trips up even people who follow cricket closely. Your tournament net run rate is not the average of your match figures. It is calculated once, over everything: all your runs, all your overs faced, all the runs against you, all the overs you bowled.
Say a team plays two games. In the first it makes 168 in 20 and concedes 140 in 20. In the second it is bowled out for 100 and the opposition knocks off 101 in 12.4 overs.
Add it up properly: 268 runs from 40 overs is 6.70 per over, and 241 runs conceded from 32.67 overs is 7.38. The tournament figure is −0.68.
Average the two match figures instead and you get −0.79. Close, but not the same — and in a group where three teams are within a tenth of each other, that gap is a qualification.
Rain, revised targets and washouts
Interruptions have their own rules. Where a match is shortened and a revised Duckworth-Lewis target is set, the revised target and revised overs are used for the side batting first, and the chasing side’s actual runs and overs are used as normal.
If a match is abandoned with no result, none of it counts. No runs, no overs, nothing carried into the calculation. A washout genuinely disappears from your net run rate — which is why a team sitting on a strong figure is often perfectly happy to see rain arrive.
What it does not tell you
The calculation ignores wickets entirely. A side that wins by one wicket off the last ball can post a better figure than a side that wins by seven, if the first chase happened to be quicker. It measures margin in runs and overs, not control.
It also rewards thrashing a weak team more than it rewards a hard-fought win over a strong one. A group decided this way is not always decided in favour of the better side, and plenty of former players say so.
But it is the rule, and it is applied consistently — much like the umpire’s call rule that keeps an LBW decision as not out even when the ball is shown clipping the stumps. You do not have to like a tiebreaker to use it.
Reading the table before the last game
Before the final group match, check whether the teams above you can be caught on points alone, because net run rate only matters once points are level. Then work out your current runs-per-over gap and ask what result closes it.
If you are chasing, the answer is a target and a number of overs. If you are batting first, it is a total and a defence. Either way you will know before the toss what the side needs — and why the batters are still swinging when the game looks won.
