Run Rate and Net Run Rate in Cricket Explained
Wiki Article
In limited-overs tournaments, teams level on points are often separated by net run rate, a number that many fans find confusing. Commentators talk about a team needing to win by a certain margin to improve its net run rate, or about run rate pressure during a chase. This guide explains run rate, required run rate and net run rate in simple terms, with examples that show how each one is calculated.
Run rate
Run rate is the average number of runs a team scores per over. It is calculated by dividing total runs by overs faced. If a team scores 180 runs in 20 overs, its run rate is 9 runs per over. Overs are counted in balls, so 10.3 overs means ten overs and three balls, which is 10.5 overs in decimal form for the calculation.
Required run rate
During a chase, the required run rate shows how many runs per over the batting team needs to win. It is calculated by dividing the runs still needed by the overs remaining. If a team needs 60 runs from 6 overs, the required rate is 10 runs per over. Comparing current run rate with required run rate shows whether the chasing side is ahead or behind.
For more explainers on cricket numbers and rules, see the Join9Wickets cricket rules section.
Net run rate
Net run rate, or NRR, is used in tournament tables. It is the team's run rate across the tournament minus the run rate conceded by the team across the tournament. A positive NRR means the team scores faster than its opponents on average; a negative NRR means the opposite.
- Runs scored rate: total runs scored divided by total overs faced.
- Runs conceded rate: total runs conceded divided by total overs bowled.
- NRR: runs scored rate minus runs conceded rate.
The all-out rule
One important detail: if a team is bowled out before using all its overs, the calculation counts the full quota of overs, not the overs actually faced. For example, a T20 side bowled out for 120 in 16 overs is treated as having faced 20 overs. This punishes collapses and is a common reason why NRR falls sharply after a heavy defeat.
A simple example
Suppose a team plays two T20 matches. In the first, it scores 160 in 20 overs and concedes 140 in 20 overs. In the second, it scores 150 in 20 overs and concedes 151 in 19 overs. Total scored is 310 in 40 overs, a rate of 7.75. Total conceded is 291 in 39 overs, a rate of about 7.46. The net run rate is about plus 0.29.
Why margins matter
Because NRR is based on rates, big wins improve it more than narrow wins. Chasing a target quickly, with many overs to spare, can also boost it significantly. Late in tournaments, teams often know they must win by a specific margin or chase within a certain number of overs to overtake a rival on NRR.
Rain-affected matches
When rain shortens a match and a revised target is set, NRR uses the revised overs and target. Matches abandoned without a result do not count in NRR at all. These rules can make the table complicated in wet tournaments.
How to use NRR as a fan
When your team is chasing in a tournament, look at both the required run rate and the qualification scenario. Broadcasters often show the target needed to overtake another team on NRR. Following these numbers turns a routine chase into a tense calculation, especially in the last round of group matches.
Key points
Run rate shows scoring speed, required run rate shows what is needed in a chase and net run rate compares scoring and conceding rates across a tournament. Remember the all-out rule, and you will understand most NRR discussions.
Listings and contact details are available on the join9wickets.com listings page.
Report this wiki page