Net Run Rate Explained for Cricket Tournaments

Net run rate, or NRR, compares a team's scoring rate with the rate it concedes across a competition stage. The important word is across. You add the runs and overs from every included match, then calculate one aggregate rate. You do not average the NRR values from separate matches.

This guide gives you the exact arithmetic, a result you can reproduce in the free net run rate calculator, and the current boundary inside CricketOrganizer. The product's live points table does not calculate NRR today.

The net run rate formula

Use four running totals for the team:

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

Suppose a team has scored 464 runs from 58.6667 decimal overs and conceded 432 from 60 overs:

Scoring rate   = 464 / 58.6667 = 7.909
Conceding rate = 432 / 60      = 7.200
NRR             = 7.909 - 7.200 = +0.709

A positive number means the team has scored faster than it has conceded. A negative number means it has conceded faster. NRR is normally shown to three decimal places, but keep the unrounded totals for the next calculation.

Convert cricket overs before dividing

The number after the dot on a cricket scorecard is balls, not a decimal fraction of an over. An innings lasting 18.4 overs used 18 overs and 4 balls:

18.4 overs = 18 + 4/6 = 18.6667 decimal overs

These common conversions are worth keeping beside the score sheet:

Do not enter 18.4 into an ordinary decimal calculation. That treats four balls as 40 percent of an over instead of four-sixths.

The calculator accepts scorecard notation in its input boxes. One display detail matters: its result panel shows cumulative overs as decimal overs rounded to one decimal place. An output of `58.7` means 58.6667 decimal overs for the calculation. It does not mean 58 overs and 7 balls, which would be impossible notation.

Calculate NRR after a match in the tool

Use the After the match mode when both innings are complete. Here is a two-match example you can reproduce exactly.

Before the second match, the team had scored 310 runs in 40.0 overs and conceded 290 in 40.0 overs. In the new match, it conceded 142 in 20.0 overs and made 154 in 18.4 overs.

1. Open the NRR calculator.
2. Leave the mode on After the match.
3. Under Season so far, enter `310` for Runs scored and `40.0` for Overs faced.
4. Enter `290` for Runs conceded and `40.0` for Overs bowled.
5. Under This match, enter `142` for Runs conceded and `20.0` for Overs bowled.
6. Leave They were all out unticked because the opponent used its full 20 overs.
7. Under Your innings, enter `154` for Runs scored and `18.4` for Overs faced.
8. Leave You were all out unticked.

The dark result panel should show +0.709 under Net run rate after this match. The four cumulative figures underneath should be 464 runs for, 58.7 decimal overs faced, 432 runs against and 60.0 decimal overs bowled.

You can audit the output without trusting the screen. Convert 18.4 to 18.6667, add it to the earlier 40 overs, then apply the formula:

464 / (40 + 18.6667) - 432 / 60 = +0.709

Apply the all-out rule correctly

When a side is dismissed before using its full allocation, standard NRR calculations charge that innings the full available quota. In a 20-over match, 112 all out after 14.2 overs contributes 112 runs from 20 overs, not from 14.3333 overs.

The calculator applies this only when you tick the relevant control:

1. Enter the runs and actual scorecard overs.
2. Tick You were all out if the batting team lost all available wickets.
3. Tick They were all out if the opponent lost all available wickets.
4. Read the effective overs in the cumulative result panel.

For a first match where your side made 112 all out in 14.2 overs and the opponent made 113 in 17.0, enter zeros under Season so far, enter the two innings, and tick You were all out. The calculator uses 20.0 overs for your innings. The calculation is:

112 / 20 - 113 / 17 = 5.600 - 6.647 = -1.047

The tool's current innings quota is 20 overs and its wicket threshold is 10. It does not expose controls for a five-over box-cricket innings or a reduced wicket count. For those formats, calculate from balls or use a separate sheet with the tournament's published quota. Do not pretend the 20-over toggle covers a rule it cannot represent.

Calculate the runs needed for a target NRR

Use Chasing a target to answer a specific planning question: how many runs must this team score over the number of overs you enter so its aggregate NRR reaches a chosen figure?

Continue with 310 runs for and 290 against from 40 overs each. The opponent has now made 160 in 20 overs. You want the team to finish on +0.500 and you are modelling a full 20-over batting innings.

1. Select Chasing a target.
2. Under Season so far, enter `310`, `40.0`, `290`, and `40.0` in the four boxes.
3. Under Their innings, already bowled, enter `160` and `20.0`.
4. Leave They were all out unticked.
5. Under The chase, enter `0.5` for Target NRR.
6. Enter `20` for Overs you'll bat.

The headline should show 170 under Runs needed to hit the target, followed by 8.50 runs an over across 20 overs. The proof is:

Runs against rate = (290 + 160) / (40 + 20) = 7.500
Required runs-for rate = 7.500 + 0.500 = 8.000
Required cumulative runs = 8.000 × 60 overs = 480
Runs needed now = 480 - 310 = 170

This mode does not know the match target, wickets remaining, a Duckworth-Lewis-Stern adjustment, or the qualification rules of another competition. Overs you'll bat is a planning denominator. If you want to model a 16-over finish, enter `16`; do not leave `20` and assume an early chase is inferred.

Keep an auditable NRR sheet

After every completed league match, add one row per team with these columns:

Store the scorecard notation and effective decimal overs. The first lets someone compare your sheet with the scorebook. The second prevents repeated conversion and rounding errors. Recalculate from the totals after each round. Never add the displayed `+0.709` to next week's match NRR.

Also publish how your competition treats shortened matches, forfeits and abandoned games. The calculator performs arithmetic on the values you enter. It does not decide which innings belong in the league regulations.

What CricketOrganizer's points table actually does

CricketOrganizer's rendered table is built by `deriveStandings` in `src/utils/standings.ts`. The same function is used on the organizer Matches > Points table tab and the public tournament table.

The current behavior is precise:

1. Every team starts with a zero row.
2. Only fixtures whose status is Completed affect the table.
3. A win earns 2 points and a loss earns 0.
4. A completed fixture with no winner and a result description containing “tie” gives both teams 1 tie point.
5. A completed fixture with no winner and no “tie” text gives both teams 1 no-result point.
6. Rows sort by points, then wins, then team name.

There is no NRR column in that rendered flow. `src/services/scheduling/standingsCalculator.ts` contains the arithmetic imported by the standalone tool, but the app table does not call it. If your tournament uses NRR, maintain the score totals separately and use the calculator as an independent check.

The cricket fixture generator hub explains the scheduling and standings workflow. The companion points-table and tiebreaker guide shows exactly how to record results and audit the visible rows.

Publish the rule before the first fixture

An organizer should be able to answer these questions before registrations close:

1. Is NRR used, and at what point in the tiebreak order?
2. Which matches count toward it?
3. What innings quota applies when a team is all out?
4. How are reduced-overs matches treated?
5. Who owns the authoritative runs-and-overs sheet?
6. When will corrections be frozen before the knockout draw?

NRR works as a tiebreaker when every input can be traced back to a scorecard and every team knew the rule. The formula is the easy part. Consistent source data is the real job.