Net run rate compares how quickly a team scores with how quickly it concedes runs. It helps explain cricket standings, including NPL coverage. Every score below is a fictional teaching example, not a result from the 2026 tournament.
The standard formula
NRR = total runs scored ÷ overs faced − total runs conceded ÷ overs bowled.
These totals cover eligible matches. The linked ICC competition conditions describe the standard aggregate calculation and the all-out adjustment. They are a reference for the cricket method, not a verified NPL 2026 rulebook. Use the NPL organiser’s conditions for competition-specific exceptions.
Example 1: both innings use 20 overs
Team A makes 180 in 20 overs. Team B makes 160 in 20 overs.
- Team A scoring rate: 180 ÷ 20 = 9.00.
- Team A conceding rate: 160 ÷ 20 = 8.00.
- Team A NRR for this example: +1.00.
Team B has the opposite figure, −1.00, for this match.
Example 2: a successful early chase
Team A concedes 150 in 20 overs, then reaches 151 in 18.4 overs.
Cricket notation counts balls after the dot: 18.4 = 18 × 6 + 4 = 112 legal balls. That is 112 ÷ 6 overs, not 18.4 decimal overs.
Team A’s rate is 151 × 6 ÷ 112 = 8.089286. Its opponents’ rate is 150 ÷ 20 = 7.5. The difference is +0.589286, displayed as +0.589 to three decimal places.
Example 3: a side is bowled out early
Suppose Team A is all out for 120 in 15 overs of an unreduced 20-over innings. Under the standard all-out rule, use its full allocation: 120 ÷ 20 = 6.00, rather than 120 ÷ 15. If the allocation was reduced, the applicable allocation and competition rules must be considered.
Example 4: combine matches before dividing
Across two full-length matches, suppose a side scores 180 and 140, each in 20 overs, and concedes 160 and 150, each in 20 overs.
Its cumulative NRR is 320 ÷ 40 − 310 ÷ 40 = +0.250. Keep unrounded totals until the final calculation. With unequal innings lengths, averaging individual match NRR values can give a different, incorrect answer.
Rain, no results and official tables
The linked ICC conditions exclude no-result games from NRR and contain rain-adjustment provisions. A DLS target can require adjusted NRR inputs; do not blindly combine raw scorecard totals after a revised target. For NPL-specific treatment, use its playing conditions and official table.
The standings guide explains the other table columns, while the playoff guide shows why league position matters.
Calculate with legal balls to avoid notation errors
For a six-ball over, convert an innings of O overs and B additional legal balls into 6O + B balls. Calculate its scoring rate as six times runs divided by that ball count. This gives the same result as dividing runs by the true fractional number of overs, while avoiding the temptation to use cricket notation as a decimal.
For example, a fictional innings of 17.2 overs contains 104 legal balls: seventeen complete overs contribute 102, then two more are added. An innings of 19.5 contains 119. The digit after the dot counts additional balls in an incomplete over; it is not a tenths-of-an-over fraction.
Wides and no-balls can add runs without adding a legal delivery to that count. For a manual calculation, use the innings totals and legal overs recorded in the scorecard rather than counting every delivery entry as a legal ball. The example assumes an ordinary scorecard and no special NRR adjustment.
An unequal-length example shows why averaging fails
Take two more fictional matches for the same team. In the first, it scores 101 in 10 overs while conceding 100 in 20. Its match-level difference is 10.1 minus 5.0, or +5.1. In the second, it scores 100 in 20 overs while conceding 101 in 10. The difference is 5.0 minus 10.1, or -5.1.
Averaging those two differences gives zero. The cumulative totals in this deliberately symmetrical example also give zero: 201 runs from 30 overs faced, against 201 from 30 overs bowled. The agreement here is a consequence of the selected numbers, not proof that averaging is the correct method.
Now change the second match so the team scores 140 in 20 overs and concedes 141 in 15. The second match difference becomes 7.0 minus 9.4, or -2.4. Averaging +5.1 and -2.4 gives +1.35. But the correct aggregate is 241 divided by 30, minus 241 divided by 35, which is approximately +1.148. The discrepancy comes from the unequal denominators.
These examples assume every innings is eligible and the stated overs are the applicable NRR inputs. No innings is treated as an early all-out innings. Those assumptions matter because an all-out or rain adjustment could change the denominator used.
Keep runs, wickets and targets separate
NRR uses runs and applicable overs, rather than a separate reward for wickets taken. Wickets can matter indirectly when a side is bowled out and the full-allocation rule applies. They do not appear as another term added to or subtracted from the standard formula.
A chase target is also different from the batting-first score. In an ordinary uninterrupted match, a side chasing 150 needs 151 to win. Use the runs actually credited in the innings, subject to the applicable NRR rules, rather than replacing its completed score with the number you expected it to reach. Rain-revised targets require additional care and should not be handled by this simple shortcut.
Use a calculation sheet that preserves the inputs
A helpful manual worksheet has one row per eligible match and columns for runs scored, legal balls faced, runs conceded and legal balls bowled. Add separate notes for an all-out allocation or another rule-based adjustment. Keep the original scorecard link so you can revisit an input if your total differs from the published table.
Sum the adjusted inputs first. Then calculate the two aggregate rates and subtract. Preserve full precision during the arithmetic and round only the final display. Repeatedly rounding each innings rate and then adding those rounded values can create another small discrepancy.
What a disagreement with the table means
If your answer differs, first check the season, included matches, legal-ball conversion and all-out treatment. Next inspect any rain-affected games and the competition’s own provisions. A scoreboard showing only rounded rates may not contain enough precision to reproduce the published total exactly.
Do not treat a small mismatch as evidence that the official table is wrong. Equally, do not change your inputs merely to force a matching answer. Identify which rule or scorecard entry explains the difference. For NPL 2026, the published competition table remains the reference for standings while its full playing conditions are needed to resolve special cases.