Virat Kohli finished the IPL 2026 final unbeaten on 75 from 42 balls. Washington Sundar, batting for Gujarat Titans in the same match, finished unbeaten on 50 from 37. Without reaching for a calculator: how much faster was Kohli scoring? Most of the Narendra Modi Stadium would have said “much faster” and left it there. The exact answer is about 43 runs per hundred balls — and it matters because almost every argument Indian fans have about batting, from who deserves to finish an innings to who should be opening, is an argument about that number, conducted by people who have never once done the division.
The 2026 final itself lasted 18 overs of chasing. Royal Challengers Bengaluru pursued 156, won by five wickets and took a second consecutive title, closing a season of 74 matches played by ten teams between 28 March and 31 May, as the season record sets out. By the following morning most of that had been compressed into three highlight clips and a single line of text.
The raw material has not gone anywhere, though. Ball-by-ball scorecards for every fixture — internationals, IPL, Ranji Trophy, the women’s domestic season — sit in public archives, and pulling up a season’s worth of cricket India results takes under a minute. What follows is not statistics for their own sake. It is the short list of calculations that turn a scorecard from a column of names into a description of what actually happened on the field.
The two rates that carry most of the argument
Cricket’s notation looks self-explanatory and mostly is not. “75* (42)” and “2/25” are compressed records of two different things, and each needs one division before it says anything at all.
Strike rate is a rate, not a total
Batting strike rate is runs scored per hundred balls faced: runs divided by balls, multiplied by a hundred. Written out with the two unbeaten innings from the final:
Kohli — 75 ÷ 42 × 100 = 178.57
Sundar — 50 ÷ 37 × 100 = 135.13
Both men were not out. Both passed fifty. One was scoring at roughly 1.79 runs a ball, the other at 1.35. Across a 40-ball stay that gap is about seventeen runs, which in a chase of 156 is the whole difference between winning with two overs spare and going to the last ball. It is also why a 30 from 15 can matter more than a 45 from 40 in the same innings — something a record list that ranks players by runs alone will never show.
Economy rate is the same division from the other end
For bowlers the convention is runs conceded per over, an over being six legal deliveries under the Laws of Cricket, which the MCC maintains as guardian of the game’s code. Rashid Khan’s 2 for 25 from four overs comes to 25 ÷ 4 = 6.25. Rasikh Salam’s 3 for 27 from four comes to 6.75. Salam took the extra wicket; Rashid was marginally the tighter of the two. Neither number on its own settles who bowled better, because phase decides difficulty — four overs at the death and four inside the powerplay are not the same job, and it is the over-by-over columns, not the summary line, that tell you which one a captain handed out.
Where the headline figure quietly misleads
Three distortions account for most bad readings, and all three are avoidable.
The first is sample size. A strike rate computed over twelve balls is noise dressed as evidence. Over a full IPL season — fourteen league games plus playoffs — it begins to describe a player. Career figures across formats describe something else again, because a Test strike rate of 55 and a T20 strike rate of 140 can belong to the same batter following two different sets of instructions.
The second is rule context. Since 2023 the IPL has operated the Impact Player regulation, under which a side names five substitutes and may introduce one during the match; before the 2026 season the BCCI confirmed the rule stays through at least 2027, despite reservations from a majority of the captains. A competition in which teams effectively bat deeper than eleven produces bigger totals and higher strike rates across the board. Setting a 2026 figure beside a 2019 figure without noting that is comparing two different games and calling it a trend.
The third is mistaking margin for performance. India’s 96-run win over New Zealand in the T20 World Cup final on 8 March 2026 — 255 for 5 against 159 — reads like total control. Their semi-final three days earlier, 253 for 7 against England’s 246 for 7, went down to seven runs, both scorelines documented in the tournament record. Nearly identical batting output, wildly different margins, because a margin describes the opposition at least as much as it describes you.
The two-minute habit
None of this needs software. It needs the scorecard read in a fixed order, every time.
Balls before runs. A fifty means very little until you know how long it took, and the balls-faced column sits right next to the runs column on every full scorecard.
Overs before wickets. Three wickets from eight overs and one from two are different afternoons entirely, and the bowling figures only make sense as a pair.
Then the phase columns, to see when a spell actually happened. Then the ground and the date — 180 at the Narendra Modi Stadium and 180 at Chinnaswamy, where the boundaries are shorter and the ball travels, are not the same 180.
Four checks. All four are printed on any complete scorecard, and all four get skipped by most of the people who then argue about selection for an hour.
The pleasure in this is not the arithmetic itself. It is that once the division becomes automatic, the game gets bigger rather than smaller. You start noticing the 22-ball innings that quietly decided a match, or the bowler who went for 34 but bowled the two overs nobody else wanted. Between a home World Cup in February and March and a 74-match league that ran to the end of May, 2026 handed Indian fans an unusual amount of material to practise on. The scorecards are all still sitting there.
