← Back to Blog

It is the second week of May. The IPL 2026 league stage is winding down. Open the points table and the fourth and fifth lines look almost identical. Both sides on 14 points. Both with one game to play. Between them sits a column of three decimal places that will decide who plays the playoffs and who books an early flight home. Net Run Rate. The number nobody pays attention to in March suddenly runs the league in May.

Fans argue about it on television panels. Captains lose sleep over it in team hotels. Most of the country thinks they understand it, and most of the country is a little bit wrong. NRR is the maths fans love to argue about and rarely understand. This piece fixes that.

The simplest version of NRR

Forget the formula for a second. NRR is your scoring speed minus the opposition's scoring speed, averaged across the entire season. If you score faster than teams score against you, your NRR is positive. If they score faster than you, it is negative. That is the whole idea. Everything else is bookkeeping.

The formula, in plain English

Now the maths. Take every run your team has scored across the league. Divide by every over your team has faced. That is your run rate for the season. Then take every run scored against you across the league. Divide by every over you have bowled. That is the opposition's run rate against you. Subtract the second from the first. The result, usually printed to three decimal places, is your Net Run Rate.

The trick is that this is not a per-match average. It is one big sum across the whole season. Runs pile into one column, overs pile into another, and the league does the long division at the end.

A worked example with simple numbers. Pretend a team plays three matches. They score 180 in 20, 200 in 20, and 160 in 18.2. Their opposition score 150 in 20, 195 in 19.4, and 161 in 19. Add up the runs you scored: 540. Add up the overs you batted, in decimal form: 58.333. Your run rate is 9.257. Now the runs against you: 506. Overs you bowled: 58.667. Their rate is 8.625. Your NRR is 9.257 minus 8.625, which works out to plus 0.632. Healthy. Comfortable. The kind of cushion captains love sitting on with one game to go.

The all-out trap that confuses everyone

Here is the rule that breaks most fans' mental model. If your team is bowled out, NRR pretends you batted your full quota of overs anyway. Bowled out for 100 in 14 overs of a 20-over chase? NRR counts your 100 as having taken the full 20.

People think this is a quirk. It is not. It is the most important rule in the system, because without it the whole thing collapses.

Think about why. A side chasing 200 is staring at a defeat. If they could just collapse cheaply in 14 overs and have those 14 overs counted, they would be giving up six overs of damage to their NRR. Get bowled out for 100 in 14, and at face value your run rate for the innings is 100 divided by 14, which is 7.142. That looks almost respectable. Meanwhile the opposition put on 200 in 20, a run rate of 10.000. The damage to your NRR is the gap, about 2.858 over those overs.

Now apply the all-out rule. Your 100 is treated as 100 in 20 overs. Run rate of 5.000. The opposition still on 10.000. Suddenly the gap is 5.000, not 2.858. The dent is much bigger. And that is the point. A team that gets bowled out has lost more comprehensively than a team that batted out its overs and finished short. NRR has to reflect that, otherwise sides would happily collapse to protect their decimal.

The same rule, applied the other way, also matters. A team chasing 150 in 20 overs that gets there in 14 overs uses only the overs actually faced. The fast finish counts in full. Bat fewer overs by chasing well, you are rewarded. Bat fewer overs because you got bowled out, you are punished. Different situations, different treatment, and that is what makes the system fair.

Three myths fans still believe

Myth 1: A six on the last ball saves your NRR. Walk into any cricket conversation in May and someone will say it. "We need to win this in 17 overs, every boundary matters, hit a six off the last ball to push the rate up." The intent is right. The maths is wildly exaggerated. NRR is averaged over hundreds of overs across the season. By the time a team has played 13 league matches, that is roughly 260 overs of batting and 260 of bowling stitched into one calculation. A single six on the last ball moves your seasonal NRR by something in the third decimal place. It can matter at the margin in a tied table. It cannot rescue a team that has been outplayed for two months. The big swings come from chasing 200 in 14 overs, not from one cleared boundary.

Myth 2: NRR breaks ties before head-to-head record. Half the country thinks head-to-head comes first. In the IPL, it does not. The order is points first, NRR second, head-to-head third. So if two teams finish on the same points and one has won both meetings between them, that is not what gets them through. NRR does. The head-to-head record is a third-level tiebreaker that almost never gets used, because NRR is so granular it produces a separation by the time you get to it. Most fans get the order wrong. Most television panels do too.

Myth 3: Wide-margin wins early in the season are wasted. Some fans think a 70-run win in March is "in the bank" and a 70-run win in May counts more because it is recent. That is not how the cumulative version works. Every margin counts equally because NRR is one continuous sum across the whole league. The big chase a side finished in 14 overs in match two of the season is still sitting in the numerator on the final day. The first half-strength match in March, when a side put 220 on the board against a stand-in attack, is doing real work in May. Captains who treat early games as throwaways pay for it later.

What captains actually do for NRR

Once a captain knows NRR could decide their playoff spot, the cricket changes. Decisions that look strange from the outside start making sense.

Look at Sunrisers Hyderabad in IPL 2024. They posted scores of 277, 287 and 266 in a stretch that left them with one of the most outrageous batting NRRs in tournament history. Some of those games were already won at the halfway stage. They kept attacking anyway, because every run scored above what felt "enough" was a deposit in the NRR account. It paid them back later when the table tightened.

Chasing teams play the same game from the other side. A side chasing 160 with eight wickets in hand will sometimes go harder in the 14th over than they did in the fourth, because they have suddenly realised they can finish in 16 overs instead of 19. Those three overs, multiplied across a season, can be the difference between fourth and fifth on the table. Travis Head finishing chases inside 15 overs at Hyderabad in 2024 was not just a batsman in form. It was a captain banking NRR.

Toss decisions shift too. Bowling first looks tactically dull on a small ground with dew. But if a side knows the opposition is likely to be bowled out for under par, chasing the target down inside the powerplay does more for NRR than batting first and posting a routine score. The maths drives the call.

The hardest call is the one most fans miss. When the opposition is collapsing and the win is sealed, the captain has to decide whether to keep attacking or coast home. Coasting feels professional. It also wastes NRR. Every wicket taken in the 18th over of a defended total counts. Every run conceded in the 19th costs. Captains chasing a playoff spot keep their fields up and their best bowlers on. The easy life is for July. Our IPL 2026 playoff race tracker has the live numbers, and the gap between fourth and fifth this year sits inside the margin a single 18th over could swing.

Why NRR survives even though everyone hates it

Every May, somebody on a panel asks why we still use NRR. Why not head-to-head? Why not a wins-only count? Why not just play a play-in match between the two tied sides?

Each alternative breaks down on inspection. Head-to-head fails when teams have only played each other once and the result was a no-result. Wins-only is exactly what got us into the tie in the first place. A play-in match makes the regular season feel cheap, and broadcasters do not want a 15th matchday they cannot sell two months in advance.

NRR survives because it does one thing nothing else does. It captures the quality of your wins and the quality of your losses in a single number. A side that hammered everyone and lost two close games sits above a side that won the same number narrowly and lost two heavily. That is the right call. The team that was better across the season finishes ahead.

The tradeoff is real. NRR can feel cold. A team that wins more matches but with smaller margins can finish below a team that won fewer matches with bigger margins, and that is hard to explain to a casual fan walking past a television. The system rewards dominance over consistency. Whether that is a feature or a bug depends on the day and the team.

What it does not do is reward a six on the last ball. The decimal does not move that much. It rewards the captain who decided to keep attacking in the 18th over of a game that was already won, two months before anyone was talking about the playoff race.