Net Run Rate Explained with Worked Examples

What net run rate actually measures

In most league and group-stage formats, teams first get sorted by points. When two or more sides finish level, the usual tie-breaker is net run rate, or NRR. It tells you how quickly a team scored compared with how quickly it was scored against.

A positive NRR means you scored faster than your opponents across the tournament. A negative NRR means the opposite. A team that wins narrowly every time can end up with a lower NRR than a team that lost once but won its other games by big margins.

That is why NRR is worth understanding before the last round of a league, not after it. Captains who know the numbers can plan whether they need to chase quickly or restrict the opposition to a certain total. Organisers who know the numbers can settle arguments in seconds.

The formula, step by step

The formula has two halves. The first half is your run rate for: total runs you scored divided by total overs you faced. The second half is your run rate against: total runs conceded divided by total overs you bowled. NRR is the first figure minus the second.

The key word is total. You add up every run and every over across all the matches that count, and only then divide. This is where most homemade spreadsheets go wrong, because averaging each match's NRR gives a different answer from the correct aggregate method.

1. List every completed match for the team, with runs scored, overs faced, runs conceded and overs bowled.
2. Replace overs faced with the full quota for any innings in which the team was bowled out. Do the same for overs bowled when the opposition was bowled out.
3. Convert every overs figure into true decimals (balls divided by 6).
4. Add up the four columns.
5. Divide total runs scored by total overs faced, then total runs conceded by total overs bowled.
6. Subtract the second figure from the first and round to three decimal places.

Converting overs: the most common mistake

Cricket overs are not decimals. The figure 18.4 means 18 overs and 4 balls. Since an over has six balls, 4 balls is 4/6 of an over, or 0.667. So 18.4 overs is 18.667 overs in maths terms.

If you type 18.4 straight into a calculator, you understate the overs faced and overstate the run rate. Across a tournament, these small errors can change who goes through. The table below gives the conversions you will use most often.

The all-out rule

When a team is bowled out before its overs are up, the calculation does not use the overs it actually batted. It uses the full quota for that innings. If a team is all out for 135 in 18.4 overs of a 20-over game, its overs faced for NRR purposes is 20, not 18.667.

The logic is simple. Losing all ten wickets ends your innings, so you have used up all of your batting resources. Without this rule, a team could collapse quickly and still post a respectable scoring rate. The rule works in reverse too: if you bowl the opposition out, you are credited with bowling the full quota.

In local cricket with fewer players, all out means whatever your league agreed, for example seven wickets in an eight-a-side game. The principle stays the same. Once a side has no batters left, count its full quota of overs.

A full three-match worked example

Here is a realistic group stage for one team, the Riverside XI, in a 20-over tournament. They won two and lost one. Watch how the all-out rule and the overs conversion both change the answer.

In match two, Riverside were bowled out for 135 in 18.4 overs, so they are credited with 20 overs faced. The opposition chased 139 in 17.2 overs, which converts to 17.333. In match three, Riverside chased 171 in 19.3 overs, which is 19.5 decimal overs.

Why you must not average match NRRs

It is tempting to work out the NRR for each match and take the average. In the Riverside example, the three match NRRs are +0.700, -1.269 and +0.269. Their average is -0.100, which is close to the true figure of -0.105 here but not the same. In tournaments with very short chases or rain-reduced matches, the gap can be much bigger.

The aggregate method weights each match by the overs actually played. A 10-over rain-reduced game should count for less than a full 20-over game, and only the aggregate method does that. Most official tournament regulations use the aggregate method, so use it in your league too.

Using NRR to plan the final group game

Before the last round, work out what result you need. Suppose your rival is on the same points and has a higher NRR. You can test scenarios: if you bat first and win by 30 runs, what does your NRR become? If you chase, how many overs do you need to finish in?

When chasing, the fewer overs you take, the higher your run rate for. When defending, the lower you restrict the opposition, the lower your run rate against. Bowling a side out also helps, because they are then charged with the full 20 overs.

Doing these sums by hand in a pavilion is slow and error-prone. Cricket Score Counter keeps tournament points tables with net run rate updated from each scored match, which saves the arithmetic and avoids the 18.4 versus 18.667 trap. It still helps to know the method so you can explain the table to anyone who questions it.

• Check which matches count. Abandoned games with no result are normally left out of NRR.
• Agree in advance how rain-reduced matches are handled, usually by using the reduced quota.
• Keep the scoresheets. Overs and balls must be exact, so a missing ball changes the result.