Explainer
Net run rate calculation in cricket, with worked examples
The net run rate formula, the all-out rule that uses the full allocation, how balls convert to overs, and what rain does to the sum, with examples.
By CricketTaken EditorialPublished Explainer19 min read
A group stage reaches its final morning and two sides are locked on the same points, so the broadcast graphic switches to a column of numbers carried to three decimal places that nobody in the studio can quite explain. Net run rate calculation in cricket is arithmetic rather than judgement, and every part of it is written down in the playing conditions, yet it is routinely described on air as a mystery. It is not a mystery. It is a subtraction with four rules attached, and three of those four rules are the ones that catch people out.
Here is the whole of it. A team's net run rate is the average runs per over it has scored across the competition, minus the average runs per over scored against it. Both halves are aggregates over every match in which a result was reached, not averages of per-match figures. If a side is bowled out, the calculation uses the overs it was entitled to rather than the overs it used. And where rain has revised a target, the side batting first is credited with a figure derived from that target rather than with the score it actually made.
The formula, written out once
The governing text sits at clause 16.10.2 of the ICC playing conditions for one-day internationals, and the equivalent clause is reproduced in event regulations such as those for the 2026 T20 World Cup. It reads that a team's net run rate is calculated by deducting, from the average runs per over scored by that team throughout the competition, the average runs per over scored against that team throughout the competition.
Written as a sum:
NRR = (total runs scored ÷ total overs faced) − (total runs conceded ÷ total overs bowled)
Four quantities, one division each, one subtraction. There is no weighting for the strength of the opposition, no adjustment for the pitch, no separate treatment of a big win against a small one beyond the runs themselves. A margin of one run and a margin of one hundred both feed the same four totals, and the second obviously moves them further.
The result is expressed in runs per over and is usually quoted to three decimal places, because group tables are frequently decided in the third one. A figure of +0.412 means the side has scored, per over, four tenths of a run more than it has conceded across the whole competition.
- 4Quantities you need per team
- 2Divisions in the formula
- 3Decimal places usually published
- 1Matches excluded from the sum, per no result
Structural features of the net run rate rule as published in the ICC playing conditions. No performance figures are involved.
Why it is an aggregate, not an average of match figures
The most common mistake made outside the scorers' box is to work out a net run rate for each match and then average them. The rule does not say that, and the two methods give different answers whenever the innings lengths differ.
An illustration, entirely constructed to expose the gap. A side plays two fifty-over matches. In the first it makes 300 from its full fifty and concedes 250 from fifty. In the second it is dismissed for 120, and its opponents knock off 121 inside twenty-two overs.
Averaging the match figures gives the first game a net run rate of six minus five, or plus one, and the second a figure of 2.40 minus 5.50, which is minus 3.10. The mean of those two numbers is minus 1.05.
The rule's own method gives something else. Runs scored total 420. Overs faced total one hundred, because the second innings is credited with the full fifty under the all-out rule discussed below. That is 4.20 per over. Runs conceded total 371 across seventy-two overs bowled, which is 5.153 per over. The net figure is minus 0.95.
The gap between minus 1.05 and minus 0.95 is not rounding. It is the difference between weighting each match equally and weighting each over equally, and the playing conditions choose the second. A short innings contributes fewer overs to the denominator, so its influence on the final number is smaller than a full one. That is why an early thrashing in a long-format tournament hurts less over time than the raw match figure suggests, and why a team cannot repair its position by playing one enormous game.
The all-out rule, and why it uses the full allocation
The second sentence of the clause is the one that does the most work: in the event of a team being all out in less than its full quota of overs, the calculation of its net run rate is based on the full quota of overs to which it would have been entitled, and not on the number of overs in which the team was dismissed.
Consider what would happen without it. A side chasing 300 collapses to 90 all out in twenty overs. Measured on overs faced, that is 4.50 an over, which is a perfectly respectable rate and a wholly absurd description of what happened. The side would have escaped most of the damage by losing badly and quickly. Worse, it would have had an incentive to keep losing wickets rather than to bat out the overs, which is the opposite of what any competition wants from its final hour.
With the rule, the same innings is entered as 90 from fifty overs, or 1.80 an over, and the arithmetic now matches the cricket. The rule closes a loophole, and it does so in a way that also credits the bowling side correctly, since the opposition's runs-conceded line is computed across that same full quota.
The consequence for a captain is real. A side facing a hopeless chase in a tournament where qualification may turn on decimals has a genuine reason to bat out its overs rather than swing at everything, because the denominator is fixed at fifty whatever happens, and every additional run is therefore free improvement. Batting time in a lost cause stops being pointless and becomes arithmetic. The judgement involved in that kind of innings is a different discipline from the one described in the guide to pacing a run chase, and it is sometimes the opposite of it.
One boundary worth naming: the rule applies to being all out, not to being behind. A side that bats its full fifty overs and scores 90 is entered at 90 from fifty as well. The rule changes nothing for teams that survive; it only prevents an early dismissal from shrinking the denominator.
The partial-over problem, and the mistake nearly everyone makes
Cricket writes overs in a notation that is not decimal. The digits after the point are balls, and they run from one to five, because the sixth ball completes the over and rolls the whole number over. There is no such thing as 18.7 overs.
That matters the moment you divide by it. An innings of 161 runs from 18.2 overs is not 161 divided by 18.2. It is 161 divided by eighteen and two sixths, which is 18.3333. The wrong version gives 8.846 an over. The right one gives 8.782. The difference is more than a twentieth of a run per over, which in a tight group is the whole argument.
The conversion is simply the number of balls over six:
| Balls shown after the point | Fraction of an over | Decimal to divide by |
|---|---|---|
| .1 | one sixth | 0.1667 |
| .2 | two sixths | 0.3333 |
| .3 | three sixths | 0.5000 |
| .4 | four sixths | 0.6667 |
| .5 | five sixths | 0.8333 |
Two further details catch people out. Wides and no-balls add runs without adding balls, so an over containing three wides still counts as one over in the denominator while contributing its runs to the numerator. And an unfinished over at the end of a completed chase counts as the fraction actually bowled, not as a whole over, which is why the winning side's rate is sensitive to whether the boundary that ends the game comes on the first ball of an over or the fifth.
That last point has a strategic edge. A side chasing a small total in a tournament decided on net run rate is not indifferent between winning off the first ball of the eighteenth over and winning off the last. The denominator shrinks with every ball saved, and a smaller denominator with the same numerator produces a larger rate. Broadcasters describe this as chasing for run rate; the mechanism is the fraction, not the aggression.
Worked example one: a completed match with a full quota
Every example that follows is constructed to make the arithmetic legible. None of them describes a real match.
Team A bats fifty overs and scores 280. Team B is dismissed for 240 in 43.2 overs.
Team A's line. Runs scored 280, overs faced fifty, so 5.600 per over. Runs conceded 240, and because Team B was all out the overs bowled are entered as the full fifty rather than 43.2, so 4.800 per over. The net figure for the match is plus 0.800.
Team B's line. Runs scored 240 across a credited fifty overs, so 4.800. Runs conceded 280 across fifty overs bowled, so 5.600. The net figure is minus 0.800.
Notice the symmetry. In a match where both sides are credited with the same number of overs, the two net figures are equal and opposite. Net run rate is a zero-sum quantity within a single game, and it only stops being zero-sum across a tournament because different matches have different innings lengths.
Worked example two: a chase completed early
Team C makes 160 from its twenty overs. Team D reaches 161 for four in 18.2 overs.
Team D's line. The numerator is 161. The denominator is 18.3333, giving 8.782 per over. Against that, 160 conceded from twenty overs bowled is 8.000. The match net figure is plus 0.782.
Team C's line is the mirror: 160 from twenty is 8.000, and 161 conceded from 18.3333 overs bowled is 8.782, so minus 0.782.
Now change one thing and nothing else. Suppose the winning runs come three balls later, at 161 for four from 18.5 overs. The denominator becomes 18.8333, the rate becomes 8.549, and the match net figure falls to plus 0.549. Three deliveries, with the identical result and the identical margin, have moved the number by nearly a quarter of a run per over.
That sensitivity is the reason a chasing side in the last group match sometimes appears to be playing recklessly with the game already won. It is not recklessness. It is the only lever available, because the runs scored figure is capped at one more than the opposition made, and the only remaining variable is how few balls it takes.
Worked example three: why the loser's collapse helps the winner twice
Team E posts 250 from fifty. Team F is bowled out for 150 in 34.4 overs.
Team F's batting line uses the full quota by rule, so 150 from fifty is 3.000 per over. Team E's bowling line uses the same fifty, so it has conceded 3.000 per over rather than the 4.331 that 150 from 34.4 overs would give.
The effect runs in both directions at once. The losing side's scoring rate is dragged down, and the winning side's concession rate is dragged down with it, which improves the winner's net figure. A bowling side that dismisses the opposition cheaply and quickly is rewarded twice over: once in the margin of victory, and again in the denominator it is credited with. That is a deliberate feature. A tournament that wanted to reward taking ten wickets could hardly do it more directly.
Bowling figures themselves are unaffected by any of this, and the distinction between what an individual bowler's economy rate measures and what a team's concession rate measures is set out in the piece on economy rate, average and strike rate.
Worked example four: assembling a tournament figure
Individual matches are only the raw material. What a points table shows is the aggregate, and building one by hand is the quickest way to see how the pieces interact.
Take a constructed group in which one side plays three fifty-over fixtures.
In the first, it scores 260 from its fifty overs and dismisses the opposition for 210 in 45.1 overs. The opposition were all out, so their innings enters as 210 from fifty.
In the second, it is itself bowled out for 180 in 41.3 overs, and the opposition reach 181 for three in 38.2 overs. Its own innings enters as 180 from fifty. The chase enters as 181 from 38.3333.
The third fixture is washed out with no result and contributes nothing to either column.
| Match | Runs for | Overs faced | Runs against | Overs bowled |
|---|---|---|---|---|
| One | 260 | 50.0000 | 210 | 50.0000 |
| Two | 180 | 50.0000 | 181 | 38.3333 |
| Three | excluded | excluded | excluded | excluded |
| Totals | 440 | 100.0000 | 391 | 88.3333 |
The scoring rate is 440 divided by one hundred, or 4.400. The concession rate is 391 divided by 88.3333, or 4.426. The net figure is minus 0.026.
That result is worth sitting with. The side won one match by a distance and lost the other with a little over eleven overs unused, and it emerges fractionally below zero. Nothing about the table is unfair; the arithmetic simply reflects that being dismissed for 180 while the opposition needed fewer than thirty-nine overs is a heavier defeat than a fifty-run win is a victory.
Why the two halves have different denominators
The table above contains a detail that surprises people the first time they meet it: the total overs faced and the total overs bowled are not the same number. One hundred against 88.3333, in a group of two completed fifty-over matches.
That is correct and inevitable. The two halves of the formula are measured over different sets of innings. Overs faced counts the side's own batting, with the full-quota rule applied where it was dismissed. Overs bowled counts the opposition's batting, with the same rule applied to them. Whenever one side is bowled out and the other is not, or a chase finishes early, the two totals diverge.
The practical consequence is that the two rates cannot be combined by adding runs and overs into a single pool. They have to be divided separately and then subtracted, in that order. Doing the subtraction first, or pooling the four totals into one division, produces a number that is not the net run rate and will not match the published table.
It also explains why a chase that ends early hurts the bowling side's figure more than the same runs conceded across a full innings. The runs go into the numerator and the unused overs never reach the denominator, so the concession rate rises on both counts at once.
- Check that a result was reachedOnly matches with a result count. A no result contributes nothing at all, so a washed-out fixture leaves both sides' figures exactly where they were.
- Decide what score to credit each sideNormally the actual totals. Where a target was revised for rain, the side batting first is credited from the revised target instead, and where the match was abandoned with a result, from the par score at abandonment.
- Fix the overs for each inningsOvers actually faced, converted from ball notation into sixths, unless the side was all out, in which case the full quota it was entitled to is used instead.
- Add the innings to two running totalsRuns scored and overs faced go into one pair of totals for the tournament. Runs conceded and overs bowled go into the other. Nothing about the individual match is stored beyond these four numbers.
- Divide once at each endTotal runs scored divided by total overs faced gives the scoring rate. Total runs conceded divided by total overs bowled gives the concession rate.
- Subtract, and publish to three placesThe concession rate is taken away from the scoring rate. The result is the figure the points table shows, and it is recomputed from the aggregates after every match rather than adjusted.
The sequence set out in the ICC playing conditions. Each step is a rule rather than a convention, and the order matters.
What rain does to the sum
Rain-affected matches are where the definition stops being obvious, and the playing conditions handle them in two distinct ways depending on how the game ended.
Where a match is played to a conclusion but a revised target had been set earlier, the side batting first is credited with one run fewer than the final target score for the side batting second, off the total number of overs allocated to the side batting second to reach that target. Its own actual score and its own actual overs are set aside for this purpose.
The logic is straightforward once stated. A revised target expresses what the first innings was worth in the currency of the second innings' shorter allocation. Comparing the raw first-innings total against a chase of a different length would compare two things measured on different scales. Taking the target minus one puts both innings on the same footing, because the target minus one is by definition the score that would have produced a tie.
Where a match is abandoned but a result is still achieved by the rain method, the first side is credited instead with the par score at the moment of abandonment, off the same number of overs the chasing side actually faced. Again both innings end up denominated in the same number of overs.
Neither provision changes the chasing side's own line, which is entered exactly as it stands: the runs it made, over the overs it used, with the all-out rule applied if it was dismissed.
This article deliberately does not re-derive how those revised targets and par scores are produced, because the resource model behind them is a separate subject in its own right and is covered in full in the explanation of how Duckworth-Lewis-Stern works. For net run rate purposes, the target is an input. Where it came from does not change the arithmetic that follows.
No results, super overs and forfeits
Three edge cases finish the rule.
No result. Only matches where results are achieved count towards the calculation. A match abandoned without a result contributes nothing to either side's totals, and the points are shared under the competition's own points system. A team whose group contains two washouts is judged on fewer overs than its rivals, which increases the leverage of each remaining match rather than reducing it.
Super overs. The event playing conditions state directly that the super over is not included in the net run rate calculation. A tied match therefore enters both sides' figures as two completed innings with identical run totals, and the eliminator that decided the points leaves no trace on the table's right-hand column. The winner takes the points; the run rate line records a tie.
Forfeits. Where a match and its points are awarded to a side because the other refused to play, the defaulting team's figure is penalised specifically: the full twenty overs of its innings in the forfeited match are counted in the calculation of its average runs per over. The side awarded the match has neither runs nor overs from that fixture entered, so its own figure is untouched. The asymmetry is intentional, since a team that turns up should not have its statistical position altered by an opponent's decision.
Where net run rate sits in the order of tie-breaks
It is worth being precise about when the number is consulted, because it is consulted later than most viewers assume.
In a bilateral series arrangement under the standard one-day playing conditions, teams level on points are separated first by the number of wins, then by wins against the other sides that are equal on points and wins, and only then by the highest net run rate.
At the 2026 T20 World Cup the group ordering runs in the same spirit. Teams level on points are separated first by the greatest number of wins in the group. If sides are still equal on points and wins, the higher net run rate takes the higher position. If that leaves them level, the head-to-head match between them decides. If that still fails, or if every match in a group produced no result, the teams are ordered by their position on the published T20I team rankings as at a date fixed in the regulations before the event.
Two things follow. A side cannot use a large net run rate to overtake a team that has won more matches, because wins are consulted first. And the figure is a separator rather than a currency, which is why the phrase "a good net run rate" has no absolute meaning. It matters only relative to whoever else finishes level.
The formats in which these tables actually get used, and the number of matches each side plays before the arithmetic bites, differ from event to event; the structures are set out in the guide to how the Asia Cup format works and in the comparable pieces on the global tournaments.
What net run rate rewards, and what it distorts
The measure has real virtues. It is transparent, it needs no model, it can be recomputed by anyone with the scorecards, and it responds to both halves of a team's performance rather than only to results. A side that wins narrowly three times sits below a side that wins heavily three times, which is a defensible thing for a tie-break to say.
The distortions are equally real, and worth naming precisely.
It ignores the opposition. Runs scored against the weakest side in a group count exactly as much as runs scored against the strongest, so a fixture list that front-loads easy games can produce a flattering figure that says more about the draw than the team.
It rewards margin in a sport where margin is often not being contested. A side chasing 140 with eight overs to spare is not trying to maximise anything except certainty, and a captain who takes risks late in a won game to shave the denominator is playing the table rather than the match.
It is dominated by innings length. Because the denominators are overs rather than matches, a single high-scoring twenty-over game moves a T20 tournament figure much less than a single fifty-over game moves an ODI one, and a heavy defeat in which a side batted its full quota costs less than the same defeat compressed into thirty overs.
It also travels beyond the international game largely unaltered. Domestic and franchise competitions overwhelmingly adopt the same clause, including the full-quota provision and the treatment of revised targets, which is why a league table in a twenty-over tournament can be read with exactly the habits described here. What differs between competitions is the tie-break order sitting above the figure, and occasionally the points awarded for a tie or an abandonment. The arithmetic underneath is portable; the ranking rules around it are not, and the regulations for each event are the only place to settle which applies.
And it says nothing about wickets. Two sides can post identical figures having lost twenty wickets and four respectively. That is why some competitions add a wickets-based separator further down the tie-break list, and why the glossary of cricket statistics treats run rate and wicket cost as answering different questions.
How to read a points table on the last morning of a group
Some practical habits, for the day when a table decides a tournament.
Start with points, then wins, then the tie-break order printed in that competition's regulations, and only then look at the right-hand column. Broadcasters lead with net run rate because it is the number that changes; it is rarely the first thing that separates anybody.
When a commentator says a side must win by a given margin, check whether the target is stated in runs or in overs. Those are different calculations. A side batting first is moving its numerator, and needs a margin. A side batting second is moving its denominator, and needs balls saved. The second is usually the larger lever.
Remember that both halves move together. Beating a side by eighty runs improves your own figure and worsens theirs by an identical amount within that match, so overtaking a direct rival is twice as efficient as beating anybody else by the same margin. Late in a group the identity of the opponent matters as much as the size of the win.
Check whether the fixture was rain-affected before trying to reconcile the table with the scorecards. If a target was revised, the first side's line in the table will not match the total on the scorecard, and the difference is the rule rather than an error. The columns to compare are set out in the guide to reading a cricket scorecard.
And treat any figure quoted to one decimal place with suspicion. Groups have been decided in the third, and rounding a tie-break to a tenth throws away exactly the information the tie-break exists to supply.
More on tournament structures, qualification and the numbers that decide them sits under cricket, and the rest of the explainers are collected in the blog archive.
Common questions
How is net run rate calculated in cricket?
Take the total runs a team has scored across the competition and divide by the total overs it has faced. Take the total runs it has conceded and divide by the total overs it has bowled. The second figure subtracted from the first is the net run rate, and it is worked out on the aggregate of every completed match rather than by averaging the figures from individual games.
What happens to net run rate if a team is bowled out?
The calculation uses the full quota of overs the team was entitled to, not the number it actually batted. A side dismissed for 140 in 32 overs of a 50-over match is treated as having scored 140 from 50, which is a far worse rate than 140 from 32. Being bowled out is therefore expensive in a way that simply batting badly for the full allocation is not.
How do you convert 18.2 overs into a number you can divide by?
Cricket over notation counts balls after the decimal point, so the figures after the dot run from 1 to 5 rather than 1 to 9. To divide, convert the balls into sixths: 18.2 overs is 18 and two sixths, or 18.3333. Treating 18.2 as eighteen point two is the single most common error in amateur net run rate arithmetic.
Does a rain-affected match count towards net run rate?
Yes, provided a result was reached. Where a target was revised, the side batting first is credited with one run fewer than the final target off the overs allocated to the chasing side, rather than with its own actual score. Matches ending in no result are excluded from the calculation entirely.
Does a super over count towards net run rate?
No. The playing conditions state explicitly that the super over is left out of the net run rate calculation, so a tied match contributes the two completed innings and nothing else. The team that wins the super over takes the points, but its run rate line looks exactly like its opponent's.
Is a higher net run rate always better for qualification?
It only matters once teams are level, and it is not always the first tie-break applied. At the 2026 T20 World Cup, group ordering goes to the team with more wins before net run rate is consulted at all, then to head-to-head results, then to the published team rankings. Points and wins come first, and a large net run rate cannot rescue a side that has won fewer matches.
Filed under Cricket·cricket · odi · t20 · statistics · tournaments