A NRR calculator works out a cricket team's net run rate: the difference between the runs it scores per over and the runs it concedes per over. Enter the runs and overs for both innings and the calculator gives the net run rate for the match. Add your earlier totals to see the figure for the whole tournament. It runs in your browser and nothing you enter is sent anywhere.
What net run rate is
Wikipedia explains that net run rate involves subtracting the opponents' run rate from the team's run rate. A team's run rate is the average number of runs scored per over by the whole team in the whole innings. The page says net run rate is the most commonly used method of ranking teams with equal points in limited-overs league competitions, and that it was first used in the 1992 tournament.
How to use the NRR calculator
- Enter the runs and overs faced for your team and the opponent.
- Choose Yes for a team that was bowled out.
- Leave the overs in a full innings blank for 50, or enter 20 for Twenty20.
- Press Find net run rate.
The formula
The match net run rate equals the total runs scored divided by the total overs faced, minus the total runs conceded divided by the total overs bowled. For a single match, the runs scored are your innings and the runs conceded are the opponent's innings. For a tournament, the page says the overall figure is not the sum or average of the match figures. It is worked out from the totals: all the runs scored divided by all the overs faced, minus all the runs conceded divided by all the overs bowled.
Overs and balls
The page says each ball is one sixth of an over, even though cricket writes it as .1 of an over. So 48.1 overs is 48 and one sixth, and the page's example of 481 runs in 48.1 overs gives a run rate of 9.986. In the calculator, type overs the cricket way: 19.3 means 19 overs and 3 balls, which is 19.5 overs. The balls can only go up to 5.
Teams that are bowled out
If a team is bowled out, the calculation does not use the overs actually faced but the full quota of overs the team was entitled to: 50 overs for a One Day International and 20 overs for a Twenty20 match. Choose Yes in the bowled out box, and the calculator uses the quota you gave. If a team wins the match by passing the target, the overs actually used count, as in the page's example, where a team making 128 for 3 in 30.5 overs is credited with 30.833 overs.
Worked example
The page gives an example in a 50-over match. Team A scores 287 for 6 in 50 overs, a run rate of 5.74. Team B scores 243 for 8 in 50 overs, a run rate of 4.86. Team A's net run rate for the match is 5.74 minus 4.86, which is 0.88, and Team B's is minus 0.88. In another example from the page, Team A is bowled out for 127 in 25.1 overs and Team B scores 128 for 3 in 30.5 overs. Team A is credited with 50 overs, so its run rate is 127 divided by 50, and Team B's run rate is 128 divided by 30.833. The net run rate is minus 1.61 for Team A and 1.61 for Team B.
Rain, no results and ties
For a match shortened by rain where Duckworth-Lewis revised targets are set, the page says the revised targets and overs are used for the first innings, and the actual runs and overs for the second innings. If a match is abandoned or has no result, none of the runs or overs count. A tied match gives a net run rate of zero to both teams. The calculator does not apply these adjustments for you, so enter the numbers as the page describes.
Reading the result
The calculator shows the two run rates and the net run rate for the match. A positive net run rate means your team scored faster than it conceded. A negative one means the opposite. It is shown to three decimal places, because teams with equal points can be separated by a very small difference.
Building the tournament figure
To see where you stand after several games, use the optional boxes. Enter the runs you have scored and the overs you have faced in the earlier matches, and the runs you have conceded and the overs you have bowled. Each of these totals must already use the full quota for any innings where a team was bowled out. The calculator adds the current match to these totals and works out the tournament net run rate from the combined figures, as the page describes.
Planning for a target
You can use the calculator to see what a result would do to your standing. Try a lower score for the opponent, or a faster chase, and look at the change in the net run rate. A team that chases a target in fewer overs adds fewer overs to its total, which raises its run rate, so winning quickly helps the figure. Winning slowly changes it less. This is why teams chasing a small target often try to finish early.
Run rate on its own
The run rate for one innings is just the runs divided by the overs. Enter the same innings for both teams if you only want to see one run rate: the two run rates are shown separately, so you can read the first and ignore the second. For a team that scored 180 in 20 overs, the run rate is 9.00 runs per over.
Common mistakes
- Writing overs as decimals. 19.3 means 19 overs and 3 balls.
- Forgetting the full quota. A team that is bowled out gets its full overs.
- Averaging match figures. The tournament figure uses the totals.
- Counting abandoned matches. They are left out.
What next
Use this often? Add Nrr to your Home screen.
Frequently asked questions
What is an NRR calculator?
A tool that works out a cricket team's net run rate: the runs it scores per over minus the runs it concedes per over.
How do you calculate NRR?
Total runs scored divided by total overs faced, minus total runs conceded divided by total overs bowled.
What happens to NRR if a team is bowled out?
The full quota of overs is used instead of the overs actually faced, such as 50 for a One Day International or 20 for a Twenty20 match.
How do you write overs for NRR?
Each ball is a sixth of an over, so 19.3 overs is 19 and a half overs.
Do abandoned matches count in NRR?
No. If a match is abandoned or has no result, none of the runs or overs count.
Sources
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.