How Net Run Rate Actually Works in Cricket (With Examples)

When two teams finish a league stage on the same number of points, one of them goes home and the other plays the knockouts. The number that usually splits them is Net Run Rate, and almost every fan has watched a captain mention it in a post-match interview without ever being told how it is worked out. The maths is not hard, but it hides two or three traps that trip up even regular viewers. Here is the full picture, with examples you can run yourself.

What net run rate is actually measuring

Net Run Rate (NRR) is a single figure that captures how heavily a team has won or lost across the whole tournament, not just whether it won. It rewards scoring quickly and restricting the opposition, so a side that wins by 80 runs gains far more than one scraping home off the last ball.

The core formula is simple to state:

NRR = (total runs scored ÷ total overs faced) − (total runs conceded ÷ total overs bowled)

The first bracket is your average scoring rate across every match. The second bracket is the average rate at which the opposition scored against you. Subtract one from the other and you get a number that is usually somewhere between +1.5 and −1.5 in a T20 league. A positive NRR means you generally outscored opponents; a negative one means you were outscored.

The crucial word is cumulative. NRR is never calculated match by match in isolation for the table. Every run and every over from every completed game piles into one big total for and one big total against. That is why a single thrashing early in a tournament can haunt a team right up to the final league game.

The two numbers that go into it

Think of each team as keeping two running tallies through the tournament:

1. Runs scored and overs faced while batting.
2. Runs conceded and overs bowled while fielding.

At any point you can take those four totals, run them through the formula, and read off the current NRR. The points table you see online updates exactly this way after every result.

There is one conversion you must get right. Overs are written in cricket's odd notation, where 18.2 overs means 18 completed overs plus 2 balls. Those 2 balls are two-sixths of an over, so the figure you actually divide by is 18.333, not 18.2. Treating 18.2 as a plain decimal is the single most common mistake people make when checking NRR at home. Always convert the balls into sixths first.

The all-out rule that changes everything

Here is the trap that catches almost everyone. If a team is bowled out before using its full allocation of overs, the calculation still uses the entire quota, not the overs actually batted.

Say a side is dismissed for 120 in 18.2 overs of a 20-over match. You might expect the run rate to be 120 ÷ 18.333. It is not. Because they were all out, the formula uses the full 20 overs, giving 120 ÷ 20 = 6.0. The logic is that a team losing all its wickets has, in effect, failed to bat out its innings, so it is charged the full overs as a penalty.

This rule matters enormously near a cut-off. A team chasing a small total knows that being bowled out cheaply damages NRR badly, while a side defending wants to take all ten wickets precisely because it inflates the opposition's effective overs and drags their rate down.

There is a mirror to this for the chasing team. If you knock off the target without losing all your wickets, only the overs you actually used count. Win in 17.4 overs and your denominator is 17.667, which boosts your rate. So a team can lift its NRR either by piling on runs when batting first, or by finishing a chase as fast as possible.

A worked example you can check

Take a single T20 fixture. Team A bats first and makes 180 for 5 in their full 20 overs. Team B chases it down, finishing on 181 for 4 in 18 overs.

For Team A from this match:

• Scored 180 in 20 overs → rate 9.00
• Conceded 181 in 18 overs → rate 10.06
• Match NRR effect: 9.00 − 10.06 = −1.06

For Team B from the same match:

• Scored 181 in 18 overs → rate 10.06
• Conceded 180 in 20 overs → rate 9.00
• Match NRR effect: 10.06 − 9.00 = +1.06

Notice the figures are exact mirror images, because one team's scoring is the other's concession. Over a tournament these per-match swings accumulate into the season NRR. If Team B later loses a low game where it is bowled out for 90 in a notional 20 overs while conceding 91 in 14 overs, that match alone would knock roughly two runs an over off its tally, and the cumulative figure would fall sharply.

What does not count, and the rain factor

A few situations sit outside the calculation. An abandoned match or a no result is simply ignored — no runs or overs from it enter either team's totals. That is why a washout can quietly help a side with a fragile NRR, because a likely heavy defeat never gets recorded.

Rain-affected games that do produce a result are trickier. When a target is revised under the Duckworth-Lewis-Stern method, the NRR is worked out against the revised target and the revised overs, not the original innings. The par score the batting side was chasing becomes the figure used for the bowling team's concession. The principle stays the same; only the numbers shift to the adjusted version.

Tied matches that reach a result are counted in full, with both innings flowing into the for-and-against columns exactly as in any other game. The tie itself does not produce a separate adjustment.

Why captains chase the run rate, not just the win

Understanding NRR explains a lot of on-field decisions that otherwise look reckless. A team batting first with the game already won will still throw the bat in the final overs, because every extra run lifts the season figure. A side defending a total it cannot lose may keep attacking for wickets rather than containing, because bowling the opposition out applies the full-quota penalty to their overs.

In a tight league, the gap between qualifying and elimination can come down to the third decimal place of NRR. That is why broadcasters flash the live NRR during run chases late in a tournament — fans and dugouts alike are doing the arithmetic ball by ball, working out exactly how fast a team must reach a target, or by how many runs it must win, to leapfrog a rival.

A handful of practical takeaways for anyone tracking a points table:

• Win big when batting first, or chase fast when batting second — both raise NRR.
• Avoid being bowled out cheaply; the full-quota rule punishes it hard.
• Bowling the opposition out is worth more to your NRR than simply restricting them.
• A washout is neutral, so a struggling team sometimes prefers rain to a likely hammering.

NRR is a blunt instrument, and critics argue it rewards thrashing weaker sides while ignoring the quality of opposition. But it is transparent, easy to verify, and applies equally to everyone. Once you can convert overs into sixths and remember the all-out rule, you can sit with the points table and work out your team's qualification scenarios before the commentators do.