Group stages in cricket produce ties on points constantly. Six teams, five matches each, and three of them finish level far more often than not. Something has to separate them, and in almost every limited-overs tournament that something is net run rate.
It has decided World Cup semi-final places. It has ended campaigns that were, on results alone, identical to campaigns that continued. It is worth understanding properly.
The calculation
Net run rate is the difference between two averages:
- Runs scored per over, across every match in the tournament
- Runs conceded per over, across the same matches
Subtract the second from the first. A side scoring at 5.6 an over and conceding at 5.1 has a net run rate of plus 0.5. Concede more than you score and the figure is negative.
The important detail is that it is calculated across the whole tournament rather than match by match, and it is a ratio of totals rather than an average of averages. All the runs a side has scored, divided by all the overs it has faced, against all the runs it has conceded divided by all the overs it has bowled.
The all out rule
This is the part that catches people out. If a team is bowled out before using its full allocation, the calculation still uses the full allocation, not the overs actually faced.
A side dismissed for 150 in 32 overs of a 50 over match does not get credited with 4.7 an over. It is treated as 150 from 50, which is 3.0. The reasoning is sound: losing all ten wickets means the innings ended, and a side that could not bat out its overs should not be rewarded with a flattering rate for the overs it never survived to face.
The effect is severe. Being bowled out cheaply damages net run rate far more than losing narrowly with wickets in hand, which is why a heavy collapse can end a tournament campaign that the points table says is still alive.
Chasing successfully
When a side wins a chase, only the overs it actually used are counted. Reaching a target of 200 in 32 overs is a run rate of 6.25, not 4.0.
This creates the situation every tournament produces at least once: a team that has already won still batting hard, because the margin of the win matters as much as the win. Finishing a chase in 32 overs rather than 40 can be the difference between qualifying and going home, and captains are entirely aware of it.
Rain and reduced matches
Where a match is shortened, the revised overs and revised target are used, so the calculation stays proportional to what was actually played. A no result contributes nothing at all to either side.
What it distorts
Net run rate rewards beating weak sides heavily. A team that thrashes the bottom two in its group by large margins can carry a better figure than a team that beat stronger opponents narrowly, and the second team is usually the better one.
It also produces some genuinely odd cricket. Sides bat on when the match is decided, chase harder than the situation requires, and occasionally make bowling decisions that look strange until you know what the table needs. None of that is cynical. It is the correct response to the rule as written.
Alternatives exist. Head to head results between the tied sides, or points per match, or a straight run difference rather than a rate. Each has its own problems, and net run rate has the advantage of being calculable by anyone with the scorecards in front of them.
Where to see it
Every tournament page in our archive collects the matches a competition has played, season by season, so the raw material is there if you want to work a group out for yourself. Start from the tournament index, or go straight to the World Cup records, which is where net run rate has caused the most argument.
Comments 0