When two teams finish a group stage on the same number of points, the table is usually separated by one small number with a plus or minus sign in front of it: net run rate, or NRR. It has knocked favourites out of World Cups and sent outsiders into PSL and IPL playoffs. Yet many fans only see the final figure on a points table without knowing where it comes from.
This guide explains the formula step by step, the rules that catch people out, and two worked examples you can check yourself with a calculator.
The net run rate formula
Net run rate compares how fast a team scores with how fast it concedes:
NRR = (total runs scored ÷ total overs faced) − (total runs conceded ÷ total overs bowled)
The first half is the team’s own scoring rate. The second half is the scoring rate of everyone who batted against them. A positive NRR means a team scores faster than its opponents; a negative NRR means it concedes faster than it scores.
Three rules that change the numbers
1. Overs are counted in balls, not decimals
Cricket writes 19.3 overs to mean 19 overs and 3 balls. For NRR, that is converted into a true fraction of an over: 3 balls is half an over, so 19.3 overs becomes 19.5. Likewise 19.1 becomes 19.167, 19.2 becomes 19.333, 19.4 becomes 19.667 and 19.5 becomes 19.833. Using 19.3 as a decimal is the most common mistake in home-made NRR calculations.
2. A team bowled out is charged its full quota of overs
If a side is all out before its overs are used up, it is treated as if it batted for the full allocation — 20 overs in a T20, 50 in an ODI. A team bowled out for 120 in 16 overs is recorded as 120 runs from 20 overs, not 16. This rule stops a side from being rewarded for losing wickets quickly.
3. It is calculated over the whole tournament
Tournament NRR is not the average of each match’s NRR. You add up every run scored and every over faced across all matches, do the same for runs and overs conceded, and then apply the formula once. A single heavy win or loss can therefore move the figure a long way early in a competition and much less later on.
Matches abandoned without a result are left out of the calculation. In rain-affected games decided by the DLS method, competitions use the revised targets and overs set for that match.
Worked example 1: a single T20 match
Team A bats first and makes 180/6 in 20 overs. Team B is bowled out for 150 in 18.2 overs.
- Team A’s scoring rate: 180 ÷ 20 = 9.00
- Team B was all out, so its innings counts as 20 overs: 150 ÷ 20 = 7.50
- Team A’s NRR from this match: 9.00 − 7.50 = +1.500
- Team B’s NRR from this match: 7.50 − 9.00 = −1.500
Notice what happens if you forget the all-out rule and use 18.2 overs (18.333) instead: Team B’s rate would become 8.18 and Team A’s margin would shrink to +0.818. That is the difference between a comfortable and a tight qualification race.
Worked example 2: adding a second match
In its next game Team A chases 160 and gets there at 161/4 in 17.3 overs. The opponents had made 160/7 in their 20 overs.
Convert the overs first: 17.3 overs = 17.5 overs.
| Runs scored | Overs faced | Runs conceded | Overs bowled | |
|---|---|---|---|---|
| Match 1 | 180 | 20 | 150 | 20 |
| Match 2 | 161 | 17.5 | 160 | 20 |
| Total | 341 | 37.5 | 310 | 40 |
- Scoring rate: 341 ÷ 37.5 = 9.093
- Conceding rate: 310 ÷ 40 = 7.750
- Tournament NRR: 9.093 − 7.750 = +1.343
If you had simply averaged the two match NRRs (+1.500 and roughly +1.200), you would get about +1.35 — close here, but in tournaments with very uneven results the shortcut can put teams in the wrong order.
Why chasing fast matters so much
In example 2, Team A won with 15 balls to spare. Because it only faced 17.5 overs, its scoring rate went up. Had it taken all 20 overs to reach 161, its rate for that game would have been 8.05 instead of 9.20. This is why captains near the end of a league stage sometimes chase aggressively even when a win is almost certain: finishing early improves NRR.
The flip side is that a side batting first cannot gain overs in the same way. Its main NRR lever is the size of its total and how cheaply it bowls the opposition out.

Calculating “what a team needs”
Before the last round of a league, broadcasters often say a team must “win by 40 runs” or “chase it in 15 overs” to overtake a rival. Those figures come from rearranging the same formula: you add the expected runs and overs from the final match to each team’s totals and find the margin where the two NRRs cross. It is simple algebra, but it only works if the existing totals are exact — which is why official tables publish runs and overs “for” and “against” alongside the NRR itself.
Quick reference
- NRR = runs scored per over − runs conceded per over.
- Convert balls properly: x.1 = 1/6, x.2 = 2/6, x.3 = 3/6 of an over.
- All out = full quota of overs counted.
- Use tournament totals, not an average of match NRRs.
- No-result matches are excluded.
You can watch NRR change in real time during league stages on our cricket live score page and the IPL, PSL and BBL points tables.
Frequently asked questions
Can net run rate be zero?
Yes. If a team scores and concedes at exactly the same rate across the tournament, its NRR is 0.000.
Does a super over count towards NRR?
No. Under standard playing conditions, runs and overs from a super over are not included; only the main match counts.
Is NRR always the first tie-breaker?
Not always. Many competitions use number of wins first, then NRR, while some use head-to-head results. Each tournament’s playing conditions set the order, so check the specific event’s rules.
