Match maths

Net Run Rate Calculator

Work out net run rate for one match or a whole season, with the all out rule applied the way the official points table applies it.

Free, no account neededLeague officialsCaptainsScorers

Add a row for every match. Tick the all out boxes where a side was bowled out, because that changes the overs counted.

Matche 1

Net run rate

+1.000

across 1 match

Run rate for

5.000

Run rate against

4.000

Runs for

250 from 50 overs

Runs against

200 from 50 overs

Beyond the calculator

Crickslab works these numbers out ball by ball while the match is on, so nobody is doing arithmetic in the scorebook.

  • Live scoring on any phone
  • Averages and strike rates kept up to date
  • Live scores your followers can watch
Request a demoExplore the ecosystem

How this was worked out

  1. 1Run rate for250 runs / 50.0000 overs = 5.000
  2. 2Run rate against200 runs / 50.0000 overs = 4.000
  3. 3Subtract5.000 - 4.000 = +1.000
Match 1 was bowled out in 45 overs, so Bhera CC is credited with the full 50 over quota bowled.
This is the all out rule. A side dismissed inside its quota is charged the full quota of overs it was entitled to bat. Calculators that skip this produce a net run rate that does not match the official points table.
Bhera CC is scoring 1.000 runs an over more than it concedes.
Net run rate totals runs and overs across every match first, then divides once. Averaging the per match net run rates gives a different and incorrect answer.

How the number is worked out

The formula

NRR = (runs scored / overs faced) - (runs conceded / overs bowled)
runs scored
Every run your side made, added up across every match in the season.
overs faced
The overs counted against your batting. This is NOT always the overs you actually faced. See the all out rule below.
runs conceded
Every run the opposition made against you.
overs bowled
The overs counted for your bowling, again subject to the all out rule when you dismiss a side early.

Totals first, then divide once. Add every run and every over across the season and do a single division at the end. Averaging each match's net run rate gives a different and incorrect answer.

Overs are converted to balls before any division. 12.4 overs is 76 balls, which is 12.667 overs, not 12.4.

A worked example: two matches, one collapse

Your side plays two 50 over matches. In the first you make 250 in your 50 overs and bowl the opposition out for 200 in 45 overs.

In the second you are bowled out for 120 in 30 overs, and they knock off 121 in 25.2 overs.

The second match is where most calculators go wrong, because you were bowled out inside your quota.

  1. 1Match 1 batting250 runs from 50 overs. Not bowled out, so 50 overs count.
  2. 2Match 1 bowling200 conceded. They were bowled out in 45, so the full 50 overs count for you.
  3. 3Match 2 batting120 runs from 30 overs, but you were bowled out, so 50 overs count against you.
  4. 4Match 2 bowling121 conceded from 25.2 overs, which is 25.333 overs.
  5. 5Season runs and overs for370 runs from 100 overs = 3.700
  6. 6Season runs and overs against321 runs from 75.333 overs = 4.261
  7. 7Subtract3.700 - 4.261 = -0.561

Net run rate is -0.561. Had the all out rule been ignored and the 30 overs actually faced been used, the answer would have come out at -0.294, and your league table would disagree with your spreadsheet.

Rules and edge cases

The situations that change the answer, and the ones most calculators get wrong.

1

The all out rule, which most calculators skip

When a side is bowled out, its net run rate is worked out over the FULL quota of overs it was entitled to bat, not the overs it actually used. A side bowled out for 120 in 30 of its 50 overs is charged 50 overs. Playing conditions used by the ICC and by almost every league say so, and it is the single most common reason a hand built table drifts from the official one.

2

The same rule works in your favour when you bowl a side out

Dismiss the opposition inside its quota and you are credited with the full quota of overs bowled, not the overs you actually needed. That is why bowling a side out cheaply helps net run rate so much more than restricting them to the same score across the full fifty.

3

A no result contributes nothing

Matches abandoned without a result are left out of net run rate entirely. Neither the runs nor the overs count. Include them and every figure below is wrong.

4

In a DLS affected match, use the revised figures

Where a target was revised for rain, the chasing side's net run rate is calculated against the revised target and the overs it was allotted, not the original ones. Competitions vary in the detail here, so check your playing conditions before entering a rain affected match.

5

Never average the per match figures

Net run rate is a season total divided once, not the mean of each match's net run rate. The two give different answers whenever the matches differ in length, which is nearly always. Add all the runs, add all the overs, then divide.

6

Overs notation is not decimal

12.4 overs means twelve overs and four balls, which is 12.667 in decimal. Dividing by 12.4 gives a rate that is quietly wrong by about two per cent, and across a season those errors accumulate into a placing.

Frequently asked questions

Add up every run your side scored and every over it faced across the season, and divide to get your run rate. Do the same for runs conceded and overs bowled. Net run rate is the first figure minus the second.

For league officials

Crickslab keeps your points table and net run rate updated on its own

Every result feeds the standings the moment it is scored, with the all out rule and your competition's tie breaks applied. No spreadsheet, no recalculating the table on a Sunday night, no arguments about whose figure is right.

See tournament management

Last reviewed 17 August 2026. Playing conditions change, so if your competition uses a different rule, its regulations take precedence over anything here.