Net Run Rate Explained: Formula, Examples and Common Mistakes

What net run rate measures

In a league stage, teams earn points for wins. When two teams finish with the same points, the table needs a way to rank them. In limited-overs cricket that is usually net run rate, shown as the NRR column on a cricket points table.

NRR answers one question: across the tournament, did this team score faster than its opponents scored against it? A positive number means yes. A negative number means no. Zero means the two rates are equal.

Wickets play no part. A team that wins by one wicket and a team that wins by ten wickets get the same NRR if the runs and overs are the same.

The formula

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

The first half is the team’s own run rate. The second half is the run rate of its opponents. Both use totals from every counted match in the tournament so far.

Overs need one step before you divide. Scorecards write 17.3 for 17 overs and 3 balls, but an over has six balls, so 3 balls is half an over. In the maths, 17.3 becomes 17.5.

So 19.4 overs is 19 and four sixths, which is 19.667 overs.

Worked examples for one match

The examples follow one side, the Blues, through three T20 matches.

Example 1: both sides bat 20 overs

The Blues score 160/6 in 20 overs. The Reds reply with 140/8 in 20 overs. The Blues win by 20 runs.

1. Blues’ run rate: 160 ÷ 20 = 8.000
2. Run rate against the Blues: 140 ÷ 20 = 7.000
3. NRR for the match: 8.000 − 7.000 = +1.000

The Reds get the mirror image: 7.000 − 8.000 = −1.000.

Example 2: a chase that ends early

The Greens score 150/7 in 20 overs. The Blues chase it down, reaching 151/4 in 17.3 overs.

1. Turn the overs into a decimal: 17.3 overs is 17.5.
2. Blues’ run rate: 151 ÷ 17.5 = 8.629
3. Run rate against the Blues: 150 ÷ 20 = 7.500
4. NRR for the match: 8.629 − 7.500 = +1.129

The Blues are charged only the overs they used. That is why a fast chase helps NRR so much. Had they taken 19.5 overs to score the same 151, their rate would be 151 ÷ 19.833 = 7.613 and the match NRR only +0.113.

When a side is bowled out

There is one special rule. A side that is bowled out is charged its full quota of overs, not the overs it lasted. Without this rule, a team could collapse quickly and keep a healthy run rate.

Example 3: all out inside the overs

The Golds score 165/5 in 20 overs. The Blues are bowled out for 120 in 16.2 overs.

1. The Blues were all out, so they are charged 20 overs, not 16.2.
2. Blues’ run rate: 120 ÷ 20 = 6.000
3. Run rate against the Blues: 165 ÷ 20 = 8.250
4. NRR for the match: 6.000 − 8.250 = −2.250

Using the real overs would give 120 ÷ 16.333 = 7.347 and an NRR of −0.903, which is wrong. The rule cuts both ways. The Golds bowled the Blues out, so the Golds count 20 overs bowled and get +2.250.

NRR across a tournament

The NRR on a points table is not the average of the match figures. You add up all the runs and all the overs first, then divide once.

Example 4: the Blues after three matches

1. Blues’ run rate: 431 ÷ 57.5 = 7.4957
2. Run rate against the Blues: 455 ÷ 60 = 7.5833
3. NRR: 7.4957 − 7.5833 = −0.0876, which rounds to −0.088

The Blues won two of three matches and still have a negative NRR, because one heavy defeat outweighed two modest wins. Averaging the three match figures would give (1.000 + 1.129 − 2.250) ÷ 3 = −0.040, which is not the table figure.

Adding matches by hand gets slow. The Crics Live net run rate calculator keeps the running totals, applies the all-out rule and shows what a team needs from its next game.

Rain-shortened matches

Rain changes the numbers that go into the formula. Competition rules differ in detail, but the usual approach is this.

• No result: an abandoned match with no result is left out of NRR completely. Neither the runs nor the overs count.
• Shortened before the start: if both sides get 15 overs instead of 20, then 15 is the full quota. A side bowled out is charged 15 overs.
• Revised target: if the chasing side is set a new target under the DLS method, the side that batted first is usually credited with one run less than that target, over the overs given to the chasing side.

Here is the revised target case with numbers. One side scores 180 in 20 overs. Rain then cuts the chase to 12 overs with a target of 131. For NRR, the first side counts as having scored 130 runs in 12 overs, not 180 in 20. This keeps the two rates comparable.

Always check the playing conditions of the competition you are following, because they set the exact wording.

Common mistakes

• Treating 19.4 as a decimal. It means 19 overs and 4 balls, which is 19.667 overs.
• Averaging match NRRs. Add all runs and all overs first, then divide once, as in Example 4.
• Using real overs for an all-out side. A side bowled out is charged the full quota.
• Rounding too early. Keep four or more decimals until the final subtraction, then round to three.
• Counting wickets. The margin in wickets never enters the formula. Only runs and overs do.
• Assuming NRR is always the first tie-breaker. Points come first. Some competitions then look at the number of wins or the result between the level teams before NRR.

If the run rate part is new to you, start with the run rate calculator, which shows runs per over for a single innings. The scorecard guide shows where to find the runs and overs you need.