Net run rate, explained: cricket's most misunderstood tiebreaker
Net run rate decides more group-stage finishes than any other stat in limited-overs cricket, and almost nobody outside a team analyst's office can state the formula correctly. Here's what it actually measures.
The formula, in one line
Net run rate (NRR) is: (total runs scored ÷ total overs faced) minus (total runs conceded ÷ total overs bowled), added up across every match a team has played in the tournament so far. Whichever side has the higher number sits above the other on a level points table.
The scoring half is intuitive. The part that trips people up is what counts as "overs faced" when a team doesn't bat out its full innings.
The full-quota rule
If a side is bowled out before using its complete allocation of overs, its overs-faced figure for NRR purposes is still counted as the full allocation for that match — 50 overs in a completed ODI innings, 20 in a T20I — not the overs it actually needed to lose all ten wickets.
The reasoning: without this rule, a team bowled out cheaply in very few overs would post an artificially inflated run rate. A side making 150 in 30 overs of a 50-over match would show 5.00 runs per over if only the overs actually faced counted — but they didn't get to bat the other 20 overs because they ran out of wickets, not because the innings ended early by design. Counting the full 50 overs (150 ÷ 50 = 3.00) reflects that more honestly.
Why sides chase fast even after the game is won
Because NRR is cumulative, margin matters even once a result is secure. A team that overhauls a target with ten overs to spare boosts its own rate far more than a team that scrapes home off the last ball — even though both walk away with the same two points. That's the entire reason commentators talk about teams "batting through" a dead rubber, or bowlers still hunting yorkers at 5 knowingly-lost wickets down: the required run rate for the match may be irrelevant, but the net run rate for the tournament isn't.


