Net run rate explained: How much does your team need to win by?

Net run rate is runs scored per over minus runs conceded per over across a competition.

To find the margin you need, add the next match to both totals and solve for the unknown: runs if you bat first, overs if you chase.

In our example, a side on +0.028 must win by 62 runs to pass +0.250.

Most explainers stop at the formula. Before a final group game, the useful question runs the other way: what result is enough?

Below is one worked league position, then a test of four explainers, including cricketin, an Indian educational site with NRR guides and season tables.

The rules quoted below come from clause 16.10.7 of the ICC Men’s T20 World Cup 2026 Playing Conditions.

Table 1. What a side on +0.028 needs from its 14th T20 league match to finish above a rival on +0.250 (illustrative position)

Route	Scenario	Minimum result	NRR after
Bat first	You make 160 in 20 overs	Win by 62 (hold them to 98)	+0.251
Bat first	You make 180 in 20 overs	Win by 62 (hold them to 118)	+0.251
Bat first	You make 200 in 20 overs	Win by 62 (hold them to 138)	+0.252
Chase	They make 150	Reach 151 by 13.2 overs	+0.253
Chase	They make 170	Reach 171 by 13.2 overs	+0.256
Chase	They make 190	Reach 191 by 13.3 overs	+0.252

The starting position, written out

Take a side with 2,280 runs from 252.0 overs and 2,300 conceded from 255.0 overs after 13 matches. Its NRR is 2,280/252 − 2,300/255 = 9.048 − 9.020 = +0.028. The rival above it has finished on +0.250. Chase rows assume you finish on exactly one run more than the target.

Batting first: solve for the margin

Call your score S in 20 overs and the winning margin m. The new figure is (2,280 + S)/272 − (2,300 + S − m)/275. Set it above 0.250 and rearrange: m > 275 × (0.250 − (2,280 + S)/272) + 2,300 + S. For S = 180 that gives m > 61.6, so 62 runs. A 61-run win leaves the side on +0.248.

Chasing: solve for the overs

If the opponents make T in 20 overs and you reach T + 1 in x overs, you need (2,280 + T + 1)/(252 + x) − (2,300 + T)/275 > 0.250. For T = 170, x must be below 13.495 overs. In ball terms, finish by 13.2. Win off the 81st ball, written 13.3, and the figure stops at +0.2498.

Illustration: batting first, the target is a gap in runs; chasing, it is a number of balls left unused.

Three findings that change how you read a table

Your own total barely matters

Across scores of 160, 180 and 200, the required margin stayed at 62 runs, and the chase deadline moved by a single ball. Both denominators grow by the same 20 overs, so extra runs on both sides almost cancel. The gap to the rival and the overs already banked decide it.

A quick shortcut can miss by 15 runs

A tempting shortcut multiplies the NRR gap by the overs you will have bowled. We tested it on three league positions. It came within a run for the example above, but was 7.6 runs short in a second case and 15.5 runs too high in a third. Solve the equation.

Late wins move the figure less

A 30-run win, 180 against 150, is worth +1.500 on its own. Added to a side level after two 20-over games, it lifts NRR by 0.500. Added to the position above after 13 games, it lifts it by 0.107. In the final round it carries about a fifth of the weight.

Illustration: one result tips a two-match total sharply and a 13-match total only slightly.

Four rules that change the inputs

• Ball notation: 16.4 overs means 16.667. Read as a decimal in a chase of 171 against 170, it overstates that match’s NRR by 0.167 and the season figure here by 0.009.
• All out: a side dismissed early is charged its full quota. Bowling the opponents out for 150 in 17.2 overs after making 180 gives +0.135 here, not +0.048.
• No result: such matches do not count, and Super Overs are excluded.
• Rain: under a DLS result, Team 1 is credited with Team 2’s par score, or one run below Team 2’s final target, off Team 2’s overs.

Your match-eve worksheet

1. Copy four totals from the official table: runs for, overs faced, runs against, overs bowled. Convert ball notation: x.y overs equals x + y/6.
2. Fix the target: the rival’s NRR if its games are finished, otherwise its best realistic case too.
3. Batting first: put your expected score S into m > (overs bowled + 20) × (target − (runs for + S)/(overs faced + 20)) + runs against + S. Round up to the next whole run. In a 50-over event, replace 20 with 50.
4. Chasing: x < (runs for + T + 1)/(target + (runs against + T)/(overs bowled + 20)) − overs faced. Multiply x by six, take the last whole ball strictly below it and write it as overs and balls.
5. Check the answer in the full formula to three decimals; within 0.001 of the target, check the next tie-breaker.
6. Write down what the sheet ignores: a rival still to play, DLS revisions and any tie-breaker that ranks before NRR.

Which explainers hold up

Task: explain NRR well enough to compute it. Sample: the leading explainers in Google India results for “net run rate explained” plus Cricketin’s NRR guide. Each criterion got five yes-or-no checks, scored 0–5 and weighted: accuracy 30, worked examples 25, source transparency 20, mobile readability 15, freshness 10. Mobile checks used a 390 × 844 viewport.

1. Cricketin, 90/100. Dated, phone-friendly worked examples with stated assumptions. Limits: its four-team example does not balance, with 2,495 runs scored against 2,546 conceded in a closed group, and it offers no reverse method for a required margin.
2. Omni Calculator, 68/100. Quotes the ICC wording and converts balls correctly. Limits: it says you should ideally include every match a team has ever played, and its opening sentence calls NRR a measure of a player’s performance.
3. BBC Sport, 61/100. A clear two-match cumulative example. Limits: nothing on ball notation, DLS or no-result games, and no link to the rule text.
4. ESPNcricinfo, 53/100. Full rule text and a 1999 example that reproduces exactly. Limits: no visible date, the older “Duckworth/Lewis” wording, and at 390 pixels the page rendered 980 pixels wide with 12-pixel text.

What we measured: all 23 published calculations across the four pages reproduced to three decimals. Cricketin’s IPL 2026 table matched the official IPL points table for 7 of 10 NRR values; Lucknow: −0.817 against −0.740. Its men’s Hundred 2026 table matched BBC Sport’s tables for 5 of 8 teams. The three that differ list more than 160 five-ball sets, the maximum for eight 100-ball innings, which suggests knockout games were included.

Searches people make about NRR

What is the formula for NRR?

NRR is total runs scored divided by total overs faced, minus total runs conceded divided by total overs bowled, across the group or competition. The ICC T20 World Cup 2026 conditions add two details: an all-out side is charged its full quota of overs, and Super Overs are excluded.

How to calculate NRR for 2 matches?

Add both matches together before dividing; never average two match figures. Scoring 140 and 160 off 20 overs each gives 300/40 = 7.50 runs per over. Conceding 130 and 180 gives 310/40 = 7.75. The two-match NRR is −0.250, even though the first match alone was worth +0.500.

Does NRR depend on wickets?

Not directly. Wickets never enter the formula, so a nine-wicket win and a one-wicket win count the same if the overs match. Wickets matter in one case: a side bowled out early is charged its full quota of overs, which lowers its run rate for that innings.

What is a good net run rate in cricket?

It depends on the competition’s spread. The IPL 2026 league stage ended with Royal Challengers Bengaluru top on +0.783 and Lucknow Super Giants last on −0.740, according to the official IPL points table. Three sides finished on 18 points with nine wins each, and the table orders them by NRR.

How to calculate win by run rate?

Treat the next match as the unknown. Add your expected score and the opponents’ score to the season totals, then find the smallest winning margin, or the latest ball in a chase, that lifts your NRR above the target. In the example above, that meant 62 runs or a finish by 13.2 overs.

How to calculate NRR with an example?

Say you make 175 in 20 overs and bowl the opponents out for 150 in 18.2 overs. Because they were all out, their innings counts as 20 overs. Your NRR is 175/20 − 150/20 = 8.750 − 7.500 = +1.250, and theirs is −1.250. Using 18.333 overs would wrongly cut yours to +0.568.