Net run rate: how big a win do you need to qualify?
A team on +0.551 NRR needs to win by 83 runs, not just win, to cross +1.000 in its last match. Worked scenarios for bowling first, chasing and losing.
Calci Editorial · · 6 min read
Every league has the same last week. Two or three teams are level on points, and the commentators start talking about "the net run rate equation". Then they say something like "they need to win by at least 40 runs" without ever showing the working.
The working is not hard. It is just arithmetic on balls, and once you see it, you can answer your own questions: how big a win do we need, does a narrow win help, and how much does a loss hurt? This post does it for one team and one match, with every figure checked in the net run rate calculator.
The team and its position
Take a team that has played its league matches and has these season totals:
- Runs scored: 1,268 in 138.4 overs (832 balls)
- Runs conceded: 1,203 in 140 overs (840 balls)
Its net run rate is 1,268 ÷ 138.667 − 1,203 ÷ 140 = 9.144 − 8.593 = +0.551. (Overs are cricket notation, so 138.4 means 138 overs and 4 balls, which is 138.667 overs in decimals. The calculator does this conversion for you.)
It has one match left, a T20, and it is level on points with a rival sitting at +0.700. The question is the same one every fan asks: what happens to +0.551 after the last match?
First, how NRR changes after a match
Net run rate for a tournament is total runs scored ÷ total overs faced, minus total runs conceded ÷ total overs bowled. It is not an average of match NRRs. The new match adds runs and overs to the existing totals, and the sum is recomputed.
Two rules matter for the sums that follow:
- If a side is bowled out, it is charged with its full quota of overs (20 in a T20), not the overs it actually batted.
- If a side wins by chasing, the overs counted are the overs actually used.
Everything below uses these rules and the totals above.
Scenario 1: bat first and win by a margin
The team bats first and scores 180 in 20 overs. The opponent also uses its 20 overs, or is bowled out, which counts as 20 either way. New totals: 1,448 runs from 158.4 overs, and 1,203 plus the opponent's score from 160 overs.
| Opponent scores | Winning margin | New NRR |
|---|---|---|
| 150 | 30 runs | +0.670 |
| 140 | 40 runs | +0.732 |
| 130 | 50 runs | +0.795 |
| 120 | 60 runs | +0.857 |
| 110 | 70 runs | +0.920 |
| 100 | 80 runs | +0.982 |
| 90 | 90 runs | +1.045 |
| 80 | 100 runs | +1.107 |
Each extra run restricted adds about 0.006 to the NRR here, so a 10-run improvement in the margin is worth about 0.06. The reason is simple: the opponent's runs are spread over 160 overs of bowling in the season totals, so one run is 1 ÷ 160 = 0.00625 off the conceded rate.
To get from +0.551 to above +0.700, the team needs to hold the opponent to about 145 or under, a win by roughly 35 runs. To pass +1.000, the opponent must be held to 97 or fewer, which is a win by 83 runs or more. At 98 the NRR is +0.995.
The team with the +0.700 rival, then, does not need a miracle: a win by 35 runs or more is enough to overtake on NRR if the rival's own result does not change its figure. That is a big "if", and it is the next section.
Scenario 2: chasing, and why a last-ball win can hurt
The opponent sets 160 in 20 overs. Our team chases 161. The overs it uses decide the NRR:
| Chase completed in | New NRR |
|---|---|
| 20.0 overs | +0.488 |
| 19 overs | +0.545 |
| 18 overs | +0.603 |
| 17 overs | +0.661 |
| 16 overs | +0.720 |
| 15 overs | +0.781 |
| 14 overs | +0.842 |
| 12 overs | +0.966 |
Look at the first row. A win in the last over, the kind that fills a stadium, takes the team from +0.551 down to +0.488. It wins two points and loses ground on NRR, because it scored its runs at 8.05 an over, below the season rate of 9.14.
The break-even is about 18 overs and 5 balls: finish the chase by then and NRR edges up (+0.554), finish at 19 overs or later and it falls. For a team that is chasing and whose rival is on a higher NRR, there is value in finishing the chase quickly rather than coasting home, which is exactly why captains sometimes change gears when the result is not in doubt. A chase done in 16 overs gets to +0.720, just ahead of the rival.
Scenario 3: losing
Nobody plans for it, but the numbers tell you how bad a loss is.
- Bat first, score 150, and lose by chasing in 18 overs (opponent makes 151): NRR +0.367.
- Bowled out for 100 (20 overs charged), opponent chases 101 in 12 overs: NRR +0.043.
The first loss costs about 0.18. The second costs more than 0.5 and almost erases the season's work. That is why a side that cannot win still fights to lose by as little as it can: the margin of the defeat is worth real points of NRR.
The ground rules that decide whether your sum is right
Overs are balls. 17.3 overs is 105 balls, not 17.3 of anything else. Converting overs to decimals by simply typing 17.3 gives an NRR that is off, and so does adding overs as if they were decimals. The calculator takes cricket notation directly. If you want to do it by hand, convert each innings to balls, add them, and divide by 6 at the end.
An all-out side faces its full quota. A team bowled out for 100 in 12 overs is charged 20. Chasing sides who win have only the overs they used.
The opponent's NRR moves too. Every run you score off a rival is their loss, but the rival you are competing against usually plays a different opponent in the last match. Their NRR changes by their match, so your calculation is a target, not a certainty. Work out the rival's range as well as your own, and recalculate when their game ends if yours is later.
Rain changes the maths. In a rain-shortened match the target and overs are adjusted by the rules for the tournament, and NRR is calculated on the adjusted figures. A match with no result gives no NRR change at all.
Tournaments vary. Net run rate is the usual first tiebreaker after points in leagues such as the IPL, but some competitions use head-to-head or wins first. Check the playing conditions for yours.
How to do your own version
- Write down your team's totals: runs scored, overs faced, runs conceded, overs bowled. Count the full quota for every innings in which a side was all out.
- Put them into the "Tournament totals" option of the net run rate calculator to confirm the current NRR.
- Add the last match's runs and overs and read the new NRR. Try several margins.
- For a whole league, put every result into the cricket points table maker, which keeps points, wins and NRR in order, and see where each possibility leaves the table.
- Planning a league of your own? The fixture generator builds the round-robin schedule for up to 32 teams.
The short version
For a team on +0.551 with a 20-over match to play, a 30-run win gives +0.670, a 40-run win +0.732 and an 83-run win +1.001. A chase finished in the last over lowers NRR to +0.488 even though it wins the points, while one finished in 16 overs lifts it to +0.720. Count overs as balls, charge the full quota when a side is all out, and recompute from totals rather than from averages.