Last Updated: September 29, 2026 12:37 PM
Net run rate (NRR) measures how quickly a cricket team scores compared with how quickly it concedes runs. It is commonly used to separate teams that finish level on points in limited-overs league tables. A positive NRR means a side has scored at a faster overall rate than its opponents, while a negative figure means opponents have scored faster. The calculation looks simple, but all-outs, successful chases and rain-affected matches can materially change the result.
The basic net run rate formula
The formula for net run rate is:
NRR = (total runs scored ÷ total overs faced) − (total runs conceded ÷ total overs bowled)
The first part gives a team’s scoring rate, expressed as runs per over. The second gives the rate at which it has allowed opponents to score. Subtract the latter from the former to find the NRR. ESPNcricinfo describes it as the average runs per over scored by a team throughout a competition minus the average runs per over scored against it.
For one completed match, the winning side normally has a positive match NRR and the losing side has the matching negative figure. In a tournament, however, the important number is calculated from the cumulative runs and overs across all applicable matches. It is not calculated by adding or averaging each match’s NRR.
A simple one-match calculation
Consider a 50-over match in which Team A scores 251 for 8 in 50 overs and Team B is dismissed for 230 in 42 overs. Team A wins by 21 runs, but the NRR calculation does not use Team B’s actual 42 overs. Because Team B was all out, its innings is treated as the full 50-over allocation.
| Team | Runs scored | Overs used for NRR | Scoring rate | Match NRR |
| Team A | 251 | 50 | 5.020 | +0.420 |
| Team B | 230 | 50 | 4.600 | -0.420 |
For Team A, the calculation is:
251 ÷ 50 − 230 ÷ 50 = 5.020 − 4.600 = +0.420
Team B’s calculation is the reverse:
230 ÷ 50 − 251 ÷ 50 = -0.420
The full-over rule prevents a side that is bowled out early from benefiting from a high-looking scoring rate based on fewer overs. Using 230 from 42 overs would incorrectly make the losing team’s scoring rate appear higher than it should for NRR purposes.
Why an all-out innings uses the full quota
An all-out team is credited with the full quota of overs it was entitled to receive, rather than the overs it actually faced. In a 20-over match, an innings ended at 16.4 overs after ten wickets fall is treated as 20 overs for NRR. In a 50-over match, an all-out innings is treated as 50 overs.
This rule applies regardless of whether the dismissed side batted first or second. It affects both teams’ records: the dismissed team’s runs scored are divided by the full quota, while the opposition’s runs conceded are also divided by that quota. The result better reflects the fact that the all-out side did not preserve wickets to use its available overs.
Wickets otherwise do not form part of the NRR formula. A team can complete a chase with nine wickets down and still gain a strong NRR if it reaches the target rapidly. Conversely, a side can win comfortably in terms of wickets but improve its NRR only modestly if the chase takes many overs.
Successful chases can improve NRR quickly
A successful chase is calculated using the actual overs taken, provided the chasing team is not all out. Suppose Team A makes 251 for 8 in 50 overs and Team B reaches 254 for 9 in 46.3 overs. Cricket notation must be converted correctly before division: 46.3 overs means 46 overs and three balls, or 46.5 overs in decimal form.
Team B’s scoring rate is therefore:
254 ÷ 46.5 = 5.462
Team A’s scoring rate is:
251 ÷ 50 = 5.020
Team B’s match NRR is:
5.462 − 5.020 = +0.442
Because it completed the chase before the 50th over, Team B scored at a higher rate than Team A. The faster a side reaches its target, the greater the potential NRR benefit, subject to the score it is chasing and the overs used.
For readers assessing standings alongside today match predictions, this is why the target alone is not enough: the timing of a chase can be as significant as the eventual result when teams are level on points.
Overs are not decimals in cricket notation
One of the most frequent NRR errors comes from treating 19.2 overs as 19.2 in ordinary decimal terms. An over has six legal balls, so the digits after the decimal point represent balls, not tenths of an over.
The correct conversions include:
- 10.1 overs = 10 overs and 1 ball = 10.1667 overs
- 15.3 overs = 15 overs and 3 balls = 15.5 overs
- 19.5 overs = 19 overs and 5 balls = 19.8333 overs
- 46.3 overs = 46 overs and 3 balls = 46.5 overs
Using 19.2 as a decimal instead of 19.3333 changes the division and can distort the final NRR. It is safest to convert balls into fractions of six before calculating run rates, then round the final NRR to three decimal places if required.
Tournament NRR uses combined totals
A tournament table uses aggregate runs and aggregate overs, not an average of individual match NRRs. This means a short, rapid chase and a full-length innings do not carry identical weight. Every run and every eligible over contributes to the combined calculation.
ESPNcricinfo’s example from the 1999 World Cup illustrates the method. After three Group A matches, South Africa had scored 678 runs in 147 overs and two balls, which is 147.333 overs. That produced a scoring rate of 4.602 runs per over. Their opponents had scored 466 runs, with two all-out innings counted as full 50-over allocations, producing 150 overs and a conceded rate of 3.107.
South Africa’s NRR at that stage of the 1999 World Cup was therefore:
4.602 − 3.107 = +1.495
The key lesson is that a team should keep cumulative totals rather than record only the NRR displayed after each match. A previous high or low match NRR does not simply get added to the next one. Its influence changes as more runs and overs are added to the tournament record.
What happens in ties, no-results and DLS matches
A tied match still contributes its runs and overs to each team’s overall tournament NRR. The match itself produces equal scoring rates for both sides when the same applicable overs are used, but its figures can alter each team’s existing competition total.
Matches with no result do not count towards NRR. ESPNcricinfo states that only matches in which a result is achieved are included. This avoids giving NRR significance to an incomplete contest that did not produce a formal result.
Duckworth/Lewis/Stern situations require special treatment. Where a match is abandoned but a result is achieved under the method, the team batting first is credited with the other side’s par score at abandonment from the same number of overs faced by the chasing team. Where a match is completed after a revised target has been set, the side batting first is credited with one run fewer than the final target, using the overs allocated to the chasing side.
What NRR does and does not show
NRR is useful because it measures a team’s scoring pace and control of opposition scoring over a league phase. It rewards rapid chases, high-scoring wins and tight bowling performances. It also supplies a consistent numerical tie-breaker when points alone cannot separate teams.
It does not measure every aspect of performance. Since wickets are excluded, NRR is not the same thing as margin of victory. A side may win narrowly while chasing quickly, or win by a large-looking wicket margin after taking many overs. Neither situation can be understood fully from NRR alone.
Conclusion
Net run rate is best understood as a competition-wide comparison of scoring speed: runs scored per over minus runs conceded per over. Use the full quota for an all-out innings, convert ball-based overs correctly, and combine all relevant matches before dividing. Once those rules are applied, NRR becomes a practical way to read a tight limited-overs points table.
