Net Run Rate, Explained Guide

Every limited-overs tournament has two scoreboards. The visible one counts points: two for a win, one for a tie or no-result, none for a loss. The hidden one is net run rate, and it only matters when the visible one ties. It is a tiebreaker, but "tiebreaker" undersells it. It quietly shapes how teams play long before any tie exists, because every side knows that points might finish level and that the margin of every game is being banked, run by run, over by over, from the first match of the tournament.

The intuition is simple: net run rate measures not whether you win, but how decisively you win and how narrowly you lose. A team that wins four games by 100 runs and loses one by 10 wickets can finish above a team that won five thrillers and lost none. That feels wrong the first time you see it, and it is worth sitting with until it feels right. The number is not judging your cricket. It is answering one narrow question: across the whole tournament, how much faster did you score than your opponents?

A team's net run rate is its average runs per over scored across the tournament, minus the average runs per over it conceded. Both halves are simple division, summed over every completed match:

NRR = (runs scored / overs faced) - (runs conceded / overs bowled)

That is the whole method. Everything confusing about net run rate lives in the edge cases, and the edge cases are where tournaments are actually decided.

If a team is bowled out before using its full quota of overs, the calculation uses the full quota anyway. A side dismissed for 180 in 35 overs of a 50-over game counts as 180 runs in 50 overs: a rate of 3.60, not 5.14.

The reason is straightforward. Without this rule, collapsing quickly would flatter a team's rate, since fewer overs faced for the same runs means a higher average. Imagine a team bowled out for 120 in 20 overs. Counted honestly at 20 overs, that is 6.00 runs per over, a sparkling rate for a batting catastrophe. Counting the full quota turns it into 2.40, which is what the innings actually was. The rule removes both the distortion and any incentive to get bowled out in a hurry. This is written into the ICC's playing conditions, clause 16.10.2, not a convention the table compilers chose.

Note the asymmetry: the rule applies to the batting side's overs faced. If you bowl a team out in 35 overs, your bowling rate still uses the 35 overs you actually bowled. The penalty falls on the side that collapsed, which is precisely the point.

Only matches where a result is achieved count toward net run rate. Ties count normally, using the same formula. Matches with no result, or abandoned without a result, are excluded entirely: they contribute nothing to either side's runs or overs.

And in ICC events, the Super Over is not included in the calculation. The shootout decides the match, never the table. When a game goes to a Super Over, the net run rate computation stops at the end of the tied main match. It is a small detail that reveals the philosophy: net run rate measures the cricket both teams had an equal chance to play, and a Super Over is, by design, unequal.

When Duckworth-Lewis-Stern decides or reshapes a match, the playing conditions rewrite the first innings for NRR purposes:

• If the match is abandoned but a result is achieved under DLS, Team 1 is credited with Team 2's par score, off the same number of overs Team 2 faced.
• If the match is concluded with DLS applied at an earlier point, Team 1 is credited with one run fewer than Team 2's final target, off the total overs allocated to Team 2 to reach the target.

The practical effect is that winning and improving your net run rate come apart. A side can crawl to a revised DLS target, win the match, and bank a poor rate. A side can lose narrowly on DLS while its underlying scoring rate was healthy. And every washout removes a game from everyone's denominator, which is why NRR tables after a rainy tournament can look nothing like the cricket that was actually played.

This is also why CricArcade's archive does not compute net run rate at all: once a tournament has a rain-affected match, reproducing the official figure needs the allotted-overs data for those games, which the archive does not store. See the methodology note.

Net run rate is cumulative across the tournament, so margin compounds. A 100-run win banks rate that survives a later defeat. A heavy defeat drags the number down and forces a team to win bigger afterwards just to repair it. Late in a group stage, teams are not only playing to win; they are playing to win by enough. The classic endgame is a side needing victory by an absurd margin, with everyone knowing the exact number from the first ball.

The dynamics differ depending on which innings you play, and this is where captains earn their money:

• Batting first: your rate is locked the moment your innings ends. A big total banked in the full quota is pure profit, and every run your bowlers then save multiplies it. The nightmare is the heavy defeat: bowled out for 150, and the damage is done before the chase begins.
• Batting second: your overs faced stop when you win. Chasing 200 in 19 overs banks a far better rate than chasing it in 20 overs with one wicket standing, even though both are the same result on the points table. This is why teams chasing small targets sometimes keep attacking with the game already won: the points are safe, and now they are mining rate.

And there is a cruel corollary for the losing side. A narrow loss batting first, say 299 all out against 300 for 4, barely dents your rate. A narrow loss batting second, falling one run short, costs you the full quota of overs for almost no runs gained. Not all defeats are equal, and the table knows it.

At the 2019 World Cup, New Zealand lost their last three group games and finished level with Pakistan on 11 points. The fourth semi-final place went to New Zealand on net run rate. Here is the final table exactly as published, not computed here:

Read the two tied rows. New Zealand at +0.175, Pakistan at -0.430: a gap of 0.605 runs per over across nine games. Where did it come from? Pakistan's campaign included a defeat by the West Indies in which they were bowled out for 105, and under the all-out rule that counts as 105 in 50 overs, a catastrophic entry in the ledger that four straight wins could not wash out. New Zealand, meanwhile, had banked huge early wins, including a 10-wicket demolition of Sri Lanka, before their late slump. The tiebreaker was not decided in the final week. It was decided in the first.

Pakistan's final game became the famous piece of NRR theatre: to overtake New Zealand they needed to beat Bangladesh by more than 300 runs, or chase any target within a handful of overs. They won the match and went home anyway. That is what "decided on net run rate" looks like in practice: not a technicality, but a margin target everyone could see and nobody could reach.

Myth 1: NRR is your average margin of victory. It is not. It is the difference between two tournament-long scoring rates. A team can have a positive NRR with a losing record if its defeats were narrow and its wins were landslides, and a team can have a negative NRR while winning more than it loses.

Myth 2: Beating a team head-to-head settles a tie. It does not, in ICC events. New Zealand lost to Pakistan at Edgbaston in 2019 and still finished above them. Head-to-head is irrelevant to the tiebreaker; the whole tournament is the sample.

Myth 3: A win always helps your NRR. A win always helps your points, but a sluggish win can leave your rate nearly unchanged while a rival's big win moves theirs. In the final week of a group, the question is never just "did we win" but "did we win by enough, and did they win by more."

Two quick scenarios, with answers:

1. Team A is bowled out for 200 in 40 overs of a 50-over match. What goes into the NRR calculation: 200 in 40, or 200 in 50? 200 in 50. The all-out rule uses the full quota.
2. Team B chases 150 and wins by 9 wickets in 25 overs. Team C chases 150 and wins by 1 wicket in 50 overs. Same points, but whose NRR benefits more? Team B, by a distance. Team B's rate for the match is 6.00; Team C's is 3.00. The points table cannot tell these two wins apart. The rate column can.

CricArcade's match archive cannot reproduce official net run rate figures once a tournament includes a rain-affected match, because the archive does not store allotted overs for those games. This guide explains the method; every NRR figure in it is reproduced exactly as published by the cited source, not computed from the archive.

For the mechanism that rewrites a match when rain gets involved, see how Duckworth-Lewis-Stern works. The other number every chase carries is covered in required run rate, and why chases collapse. And for the tournament shape net run rate has had to operate inside across five decades, see how the World Cup format changed, 1975 to 2023.

• ICC Men's ODI playing conditions, clause 16.10 (net run rate)
• 2019 Cricket World Cup, group stage standings
• ESPNcricinfo, ICC Cricket World Cup 2019

• How to Draft a World Cup XI: The roll-pick-skip mechanic behind The Chase, the six team templates, and what it actually takes to chase 380 without losing a wicket.
• How to Chase a Big ODI Total: Required run rate, wickets in hand, and pacing an innings across the powerplay, middle overs and death: why the team that panics first usually loses.
• Can You Chase 380? The Scoring Ceiling and the Elite Floor: Why a 50-over total tops out near 380, how elite line-ups are protected from collapse, and what it actually takes to reach the top of the range.
• ODI Powerplays, 1971 to Today: Field restrictions began as a fix for dead opening overs and have been rewritten roughly every decade. What each rewrite changed, and what the archive says it did to scoring and to wickets.
• Play The Chase, or browse every guide.