1. The Formula
Net run rate is the run rate a team scores at, minus the run rate it concedes at. Take the total runs a team has scored divided by the total overs it faced, then subtract the total runs it conceded divided by the total overs it bowled. A positive NRR means the team scores faster than it lets the opposition score.
That is the whole formula. Everything else on this page is about applying it correctly — because two details trip people up, and both change the answer.
2. Converting Overs Correctly
Cricket writes overs in a way that is not decimal. "18.3 overs" means 18 overs and 3 balls — not 18.3 in the mathematical sense. Since an over is six balls, 3 balls is 3 ÷ 6 = 0.5 of an over, so 18.3 overs becomes 18.5 in decimal before you divide. Skip this conversion and every part-over gives a wrong NRR.
Quick conversions to keep in mind:
| Cricket notation | Balls | Decimal overs |
|---|---|---|
| 18.0 | 108 | 18.000 |
| 18.1 | 109 | 18.167 |
| 18.2 | 110 | 18.333 |
| 18.3 | 111 | 18.500 |
| 18.4 | 112 | 18.667 |
| 18.5 | 113 | 18.833 |
There is no 18.6 — after the sixth ball the over is complete and it becomes 19.0.
3. Single-Match Example
Your team scores 165 in 20 overs, then bowls the opposition out for 120, also in 20 overs.
- Your run rate: 165 ÷ 20 = 8.25
- Their run rate: 120 ÷ 20 = 6.00
- NRR for this match: 8.25 − 6.00 = +2.25
A big positive number, because you scored fast and restricted them. Now here is where it gets interesting — what if you were the team bowled out?
4. The Bowled-Out Rule
When a team is bowled out before using its full overs, the NRR calculation uses the full quota of overs, not the actual overs the team faced. A side bowled out for 120 in 17.4 overs of a 20-over match is treated as having batted the full 20 overs. This is deliberate — it penalises losing all your wickets, and stops a team protecting its run rate by being dismissed cheaply in few balls.
Take that bowled-out side: 120 all out in 17.4 overs, 20-over match.
- Wrong — using actual overs: 120 ÷ 17.667 = 6.79
- Right — using full quota: 120 ÷ 20 = 6.00
The difference is large, and it always works against the team that was bowled out. This one rule is what most online NRR calculators get wrong.
5. Tournament NRR
Across a tournament, NRR is not the average of your match NRRs. You aggregate everything first.
For a tournament, add up all the runs you have scored and all the overs you have faced across every match, and separately all the runs conceded and all the overs bowled. Then apply the formula once. Averaging individual match NRRs gives a different, incorrect answer, because it ignores that matches have different run totals and over counts.
Two group games:
| Match | You scored | You conceded |
|---|---|---|
| Game 1 | 180 in 20.0 | 175 in 20.0 |
| Game 2 | 150 in 20.0 | 152 in 18.2* |
| Aggregate | 330 in 40.0 | 327 in 38.2 |
*The opposition chased 152 and won in 18.2 overs. They were not bowled out — they won — so their actual overs count. Now aggregate:
- Your run rate: 330 ÷ 40.0 = 8.25
- Conceded run rate: 327 ÷ 38.33 = 8.53
- Tournament NRR: 8.25 − 8.53 = −0.28
Despite winning Game 1 comfortably, conceding a fast chase in Game 2 pulled the aggregate NRR negative. That is exactly the kind of swing that decides qualification.
6. Chasing to Qualify
Late in a group stage, teams often know they must win and lift their NRR above a rival's. Say your rival sits on +0.40, and your figures so far are 900 scored in 100 overs, 850 conceded in 100 overs — an NRR of +0.50. You need to chase 161 to win. How fast?
| Win chasing 161 in… | New NRR |
|---|---|
| 20.0 overs | +0.42 |
| 18.0 overs | +0.57 |
| 16.0 overs | +0.72 |
| 15.0 overs | +0.80 |
Winning slowly barely moves you; winning in 16 overs jumps your NRR to +0.72, comfortably clear. This is the maths captains are doing in the dugout during a run chase — and it is exactly what the net run rate calculator works out instantly if you would rather not do it by hand.
Doing This Automatically
For a single match the arithmetic is quick. Across a tournament, keeping every team's aggregate runs and overs current after each match — and applying the bowled-out rule correctly each time — is where mistakes creep in, and one wrong number changes who qualifies.
If you run a league, tournament management in the app keeps every team's points table and NRR updated automatically as matches are scored, using this exact method — the same one the IPL points table uses.