Net Run Rate Explained, With a Worked Example

By the Live Cricket Zone editorial team · Last reviewed 17 September 2026

Net run rate, or NRR, is the tie-breaker used in almost every limited-overs league and tournament group when sides finish level on points. It is a measure of how much faster a team has scored than it has conceded across all its matches. The formula is short, but two details in how it is applied catch people out every tournament.

The formula

Net run rate = (total runs scored ÷ total overs faced) − (total runs conceded ÷ total overs bowled), calculated across every match the team has played in the competition.

Both halves are run rates, in runs per over. A positive NRR means a side has scored faster than its opponents scored against it; a negative NRR means the opposite. The totals are cumulative for the tournament, not an average of per-match figures, so a heavy defeat in one game can drag a side's NRR down for the rest of the group stage.

Detail one: being bowled out

If a side is dismissed before its overs run out, it is treated as having faced its full quota of overs. A team bowled out for 150 in 35 overs of a 50-over match is recorded as scoring 150 from 50 overs, a run rate of 3.00, not 4.29. The same applies to the bowling side: the runs they conceded are divided by the full 50 overs. This rule prevents a side from being rewarded for a fast collapse and is the single most common cause of confusion when NRR is being calculated at the end of a group.

Detail two: overs and balls

Overs are counted in balls, not as decimals. An innings of 47.3 overs is 47 overs and three balls, which is 47.5 overs for calculation purposes (47 plus 3⁄6). Forgetting this and treating 47.3 as a decimal introduces small errors that can matter when two sides are separated by a few thousandths.

Rain, DLS and no-results

  • If a match is decided by the DLS method, the side batting second is credited with a score of one run fewer than its revised target from its revised overs, and the side batting first is credited with the runs it actually made from the overs it actually faced.
  • If the match is a no-result, it is excluded from both sides' NRR entirely; only the shared points count.
  • If the chasing side wins, it is credited with the runs it actually scored from the overs it actually took, which is why chasing sides try to finish quickly when a group is tight.

Worked example

Suppose a team plays three 50-over group matches with these results (the numbers are invented for the example):

MatchRuns scoredOvers facedRuns concededOvers bowled
1280/650245/950
2 (bowled out)180 all out41.3 (counts as 50)184/338.2
3 (won chasing)223/444.4222/850
  1. Total runs scored: 280 + 180 + 223 = 683.
  2. Total overs faced: 50 + 50 (bowled out, so full quota) + 44.4 (= 44.667) = 144.667.
  3. Runs scored per over: 683 ÷ 144.667 = 4.721.
  4. Total runs conceded: 245 + 184 + 222 = 651.
  5. Total overs bowled: 50 + 38.2 (= 38.333) + 50 = 138.333.
  6. Runs conceded per over: 651 ÷ 138.333 = 4.706.
  7. Net run rate: 4.721 − 4.706 = +0.015.

Notice how the bowled-out rule works against this side in match 2: its 180 runs are spread over 50 overs rather than the 41.3 it actually faced, cutting its scoring rate for that game from 4.34 to 3.60. Notice also that the opponents in match 2 chased 184 in 38.2 overs, and those 38.2 overs are what count against our side, not 50, because the chase finished early.

Why teams talk about it before the last group game

Because NRR is cumulative, a team going into its final group match usually knows exactly what margin it needs. A side batting first may need to win by a certain number of runs; a side chasing may need to reach the target within a certain number of overs. Those targets are simple to calculate from the formula above, and commentators do so live. NRR is used in the IPL, the ICC World Cups, the Champions Trophy, the Asia Cup and nearly every franchise league; the IPL guide explains where it sits in the playoff qualification rules.