Net run rate (NRR) measures how quickly a team scores runs compared with how quickly it concedes them across a tournament. Expressed as a single number, it is the average runs a side scores per over minus the average it leaks per over. It is cricket’s main tie-breaker, deciding places when teams are level on points in a league table.
What is the net run rate formula?
The formula set out in the ICC’s playing conditions is straightforward:
Net Run Rate = (Total runs scored / Total overs faced) − (Total runs conceded / Total overs bowled)
The first bracket is your team’s run rate across every completed match in the tournament. The second bracket is the run rate you allowed your opponents. Subtract the second from the first and you have the NRR. A positive result means you have scored faster than you have conceded; a negative result means the opposite.
Importantly, the calculation is cumulative over the whole competition, not a single game. Runs and overs are added up across all counting matches before the division is done, so one heavy win or loss can move the figure sharply.
How do you convert overs correctly?
A common mistake is to treat 45.3 overs as 45.3 in decimal. It is not. An over is six legal balls, so overs are counted in base six. The whole number is the completed overs and the digit after the point is the number of balls (0 to 5). To use it in the formula, convert the balls to a fraction of an over.
For example, 45.3 overs is 45 overs and 3 balls, which equals 45 + 3/6 = 45.5 decimal overs. Similarly, 19.4 overs is 19 + 4/6 = 19.667 overs. Getting this conversion right is essential, because dividing by the wrong denominator produces the wrong run rate.
Can you show a worked example?
Imagine a T20 team that plays two matches. Work through it step by step.
Match 1: Our team scores 180 in its full 20 overs. The opponent replies with 150 all out, but is dismissed in 18 overs.
Match 2: Our team scores 160 in 20 overs. The opponent chases and finishes on 161 for 4 in 19.2 overs, winning the game.
First, add up our runs scored: 180 + 160 = 340, across 20 + 20 = 40 overs faced. Our scoring rate is 340 / 40 = 8.50 per over.
Now the runs conceded. In Match 1 the opponent was all out for 150 but batted only 18 overs. Because they were bowled out, the full quota of 20 overs is used, not 18. In Match 2 they scored 161 in 19.2 overs, which is 19 + 2/6 = 19.333 overs. So runs conceded = 150 + 161 = 311, across 20 + 19.333 = 39.333 overs. The conceding rate is 311 / 39.333 = 7.91 per over.
Net run rate = 8.50 − 7.91 = +0.59. The positive figure shows the team has, on balance, scored faster than it has conceded.
| Quantity | Match 1 | Match 2 | Total |
|---|---|---|---|
| Runs scored | 180 | 160 | 340 |
| Overs faced | 20 | 20 | 40 |
| Runs conceded | 150 | 161 | 311 |
| Overs bowled | 20 (all out) | 19.333 | 39.333 |
Why does the all-out rule matter?
The rule that a dismissed side is charged its full quota of overs has a big strategic effect. Bowling a team out cheaply and quickly boosts your NRR far more than simply winning, because you get credit for restricting them to few runs while the denominator stays at the maximum overs. This is why captains often push for the last wickets even when the win is already assured.
Conversely, being bowled out early yourself is doubly damaging. You are credited only with the runs you actually made, but the full quota of overs is used against you, dragging your scoring rate down.
Which matches count?
Under ICC playing conditions, only matches that reach a result count towards NRR. Games ending in a no result — usually because of rain — are excluded entirely and have no effect either way. Where a match is decided by the Duckworth-Lewis-Stern (DLS) method, the conditions specify how the chasing side’s par or target score is credited, so that rain-affected results feed into NRR fairly rather than being ignored.
How does chasing affect net run rate?
When a team is batting second and successfully chases a target, only the overs it actually used are counted, not the full quota — because the innings ended with the win. If a side knocks off the runs in 15 of its 20 overs, its scoring rate is calculated over 15 overs, which flatters the NRR. This is why a team that already knows it needs a strong net run rate will try to reach the target as quickly as possible rather than coasting to the finish.
The same logic pushes the team batting first to score as many runs as it can and then bowl the opposition out cheaply. Both halves of the formula reward positive, attacking cricket, which is part of why administrators favour NRR as a tie-breaker: it nudges teams to play for a big margin rather than a narrow, cautious win.
What are the limitations of net run rate?
NRR is transparent and easy to recompute, but it is not a perfect measure of strength. Because it is cumulative, a single lopsided result — a huge win against a weaker side, or a heavy defeat — can distort a team’s figure out of proportion to its overall form. It also takes no account of the quality of the opposition or the difficulty of conditions; runs scored on a flat pitch count the same as runs ground out on a difficult one.
Some critics argue that alternatives, such as ranking by head-to-head results or by a points-per-innings method, would be fairer. But those systems can be harder for fans to follow mid-tournament. NRR survives because anyone with the scorecards can calculate it, and because it updates instantly as a match unfolds.
Why is net run rate used at all?
When several teams finish a group stage on the same number of points, organisers need an objective way to rank them. Net run rate rewards the manner of victory, not just the fact of it, encouraging positive cricket: batting sides chase quickly, and bowling sides try to limit the opposition. In big events such as the ICC World Cups and the Indian Premier League, the closing group games are often watched as much for their effect on the NRR table as for the result itself. A team can win and still miss out, or lose and still qualify, depending on how the margins fall.
Fans watching those final rounds keep one eye on the scoreboard and the other on the NRR column, because a single over can shift who goes through. It is not a flawless system, but it is consistent, applied the same way for every side, and simple enough that a supporter with a calculator can work out exactly what their team needs.
How can a team improve its net run rate?
There are only two levers, and both follow directly from the formula. A team can raise the first bracket by scoring faster — posting bigger totals in the same overs, or chasing targets in fewer overs. It can lower the second bracket by conceding fewer runs — bowling opponents out cheaply, or restricting their scoring rate. Winning by a wide margin does both at once, which is why a commanding victory lifts NRR far more than a narrow one.
The reverse is equally true. A team cannot ‘save’ net run rate by losing narrowly if the defeat still leaves it conceding faster than it scored. This is the practical reason captains sometimes make unusual tactical choices late in a dead rubber: with qualification hinging on decimals, the margin of victory can matter as much as the win itself.