Cricket Net Run Rate (NRR) Calculator

Background.

Net run rate is the ICC's tie-breaker for teams level on points in a group. It is defined in the playing conditions themselves, not by custom: ICC Men's One-Day International playing condition 16.10.2 states 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". The identical rule appears as clause 16.10.7 of the ICC Men's T20 World Cup 2026 playing conditions.

The part everyone gets wrong is the second sentence of that clause: "In the event of a team being all out in less than its full quota of overs, the calculation of its net run rate shall be 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." Bowl a side out for 213 in 41.2 overs of a 50-over match, and their runs are divided by 50, not by 41.33. In the worked example below that single rule is worth 0.893 of net run rate in one match — enough to reorder a World Cup group. Any calculator that divides by the overs actually bowled is not computing net run rate; it is computing something else that happens to look similar.

The second trap is the overs notation. Cricket writes 41 overs and 2 balls as 41.2, which is 248 balls, which is 41.3333 overs — not 41.2. This calculator takes both overs figures in scorecard notation, converts them at six balls to the over under MCC Law 17.1, and refuses illegal figures such as 41.7, because the digit after the point is a ball count that can only run from 0 to 5.

The calculator has two modes. 'Single match' computes one match's contribution and applies the all-out rule to either side, which is what you want when you are working out what a result would do to the table. 'Whole competition' takes the four season totals — runs for, overs faced, runs against, overs bowled — and divides them straight, because the per-match substitution has already been made when those totals were built. That is precisely how the ICC clause aggregates: it speaks of runs per over "throughout the competition", with the quota substitution applied match by match as the totals accumulate.

Three scope limits are worth stating up front. First, only matches that produced a result count — clause 16.10.2 says so explicitly, so a no-result or abandoned match is simply left out of both totals. Second, a Super Over is excluded, per the note in T20 World Cup clause 16.10.7. Third, this calculator does not implement the Duckworth/Lewis/Stern credit rules in the last part of the clause, which require a DLS Par Score or Target Score from the proprietary DLS tables. If a match in your competition was decided under DLS, look up the credited runs and overs the clause specifies and enter them by hand in the cumulative mode. Guessing them is not possible from a scorecard and the calculator will not pretend otherwise.

Net run rate is also not the first tie-breaker. Under T20 World Cup clause 16.10.4, teams level on points are separated first by number of wins, and only then by NRR, then by head-to-head, then by ICC ranking.

What is cricket net run rate calculator?

Net run rate is a difference of two rates, both measured in runs per over: the rate at which a team scores, minus the rate at which it concedes. Over a competition it is computed from aggregate totals rather than by averaging per-match figures, which matters because a team that scores 300 in 50 overs and 60 in 10 has an aggregate rate of 360/60 = 6.00, not the mean of 6.00 and 6.00 — the two happen to agree here, but they diverge whenever the innings lengths differ. NRR is quoted on an official points table to three decimal places and can be negative, which simply means a team has conceded faster than it has scored. Its purpose is narrow: it is a tie-breaker, applied after number of wins under ICC clause 16.10.4, and it is designed to reward margin of victory without rewarding it without limit. The all-out substitution is the mechanism that makes it work as a measure of dominance rather than of chance. Without it, a side bowled out cheaply in few overs would post a high run-rate-against for its opponent only if it scored quickly, and a team that dismissed the opposition for 60 in 15 overs would be penalised relative to one that conceded 60 in 50 — an absurd incentive. With it, ten wickets is treated as the consumption of the full innings, so bowling a side out is always the best outcome for NRR. The symmetrical case on the batting side is a chase: a team that wins with overs to spare divides its runs by the overs it actually used, because it was not all out and its innings ended by reaching the target.

How to use this calculator.

1. 01Pick a mode. Use 'Single match' to see what one result does to your NRR, and 'Whole competition' when you already have season totals for and against.
2. 02Enter the two team totals — your runs and the opposition's — including all extras. These are team scores, not individual figures.
3. 03Enter both overs figures in scorecard notation. 41 overs and 2 balls is 41.2, and the calculator converts it to 41.3333 overs internally. Check the 'overs used' outputs to confirm it read your part-overs the way you meant.
4. 04Set the two all-out flags honestly. If a side was bowled out inside its quota, say so — the calculator then substitutes the full quota under ICC clause 16.10.2 rather than the overs actually used. This is usually the largest single factor in the answer.
5. 05Set the quota: 50 for an ODI, 20 for a T20, or the DLS-revised innings length if overs were cut. It must be a whole number.
6. 06Read the net run rate, and read 'run rate for' and 'run rate against' beneath it to see which half is doing the work. A team can have a positive NRR by scoring heavily, by conceding little, or by bowling sides out — and knowing which tells you what to do about it.
7. 07Leave out any match with no result. Clause 16.10.2 counts only matches where a result was achieved, and a Super Over is excluded entirely.

The formula.

The rule is ICC playing condition 16.10.2 (ODI) and 16.10.7 (T20 World Cup), and it has three parts.

Part one is the subtraction. Take the average runs per over your side scored, subtract the average runs per over scored against it, and the difference is the net run rate. Both averages are computed from aggregates across the competition, not by averaging match-level rates.

Part two is the all-out substitution, and it is the whole reason the statistic behaves sensibly: "In the event of a team being all out in less than its full quota of overs, the calculation of its net run rate shall be 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." A side bowled out for 213 in 41.2 overs of a 50-over match is treated as having used 50 overs. That divides their runs by a larger number, lowering their run rate — which simultaneously raises the net run rate of the side that bowled them out. Both effects are intended: losing all ten wickets means you failed to use your innings, and dismissing a side means you took it away from them.

Part three is the overs arithmetic, which is where the implementation lives. Cricket's O.B notation is a mixed number: 41.2 means 41 overs plus 2 balls. Since an over is six balls under MCC Law 17.1 — the ICC conditions word clause 17.1 as "overs of 6 valid balls" — the conversion is balls = 6 × 41 + 2 = 248, and decimal overs = 248 ÷ 6 = 41.3333. Using 41.2 as if it were a decimal shrinks the denominator and inflates the run rate. The calculator refuses any figure with a ball digit above 5 or with more than one digit after the point, because neither can appear on a scorecard.

The worked example makes the size of the all-out effect concrete: applying the rule gives a net run rate of +1.480 for the match, and ignoring it gives +0.587. A 0.893 swing in a single group game is routinely the difference between qualifying and going home, which is why an NRR calculator that skips the substitution is worse than useless — it is confidently wrong in the direction that matters.

What is deliberately not implemented: the DLS credit rules at the end of the clause. Where a match is abandoned but a result is achieved under DLS, clause 16.10.2 credits Team 1 with Team 2's Par Score off the overs Team 2 faced; where DLS was applied earlier, Team 1 is credited with one run less than the final Target Score off Team 2's allocated overs. Both figures come from the DLS tables and cannot be derived from a scorecard, so this calculator asks you to enter them by hand in the cumulative mode rather than inventing them.

A worked example.

Frequently asked questions.

References& sources.

1. [1]International Cricket Council — ICC Men's One-Day International Playing Conditions, effective from July 2025 (PDF). Clause 16.10.2 (Net run rate): "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. In the event of a team being all out in less than its full quota of overs, the calculation of its net run rate shall be 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." Clause 17.1 defines an over as "6 valid balls"; clause 13.6.1 limits an innings to 50 overs.
2. [2]International Cricket Council — ICC Men's T20 World Cup 2026 Playing Conditions (PDF). Clause 16.10.7 carries the identical net run rate rule for a 20-over group stage and adds "Note: The Super Over is not included in the net run rate calculation." Clause 16.10.4 places NRR as the second tie-breaker, after number of wins and before head-to-head; clause 13.6.1 limits an innings to 20 overs.
3. [3]International Cricket Council — Men's ODI Match Clause 16: The Result. The ICC's HTML publication of the same playing condition, carrying the net run rate definition, the all-out full-quota rule and the requirement that "only those matches where results are achieved will count for the purpose of net run rate calculations".
4. [4]Marylebone Cricket Club — Laws of Cricket, Law 17 (The over). Law 17.1: "The ball shall be bowled from each end alternately in overs of 6 balls." This is the basis for converting scorecard notation such as 41.2 into 248 balls and 41.3333 decimal overs.
5. [5]Marylebone Cricket Club — Laws of Cricket, Law 16 (The Result). Law 16.5.1 defines a tie as occurring "when all innings have been completed and the scores are equal" — the situation that sends a match to a Super Over, whose runs and balls are excluded from net run rate.