The T20 Batting Ledger: Five Numbers That Tell Five Different Stories

1,122. That number sits at the top of this year's international T20 run-scoring list — Ishan Kishan, in 32 innings, at an average of 38.68 and a strike rate of 170.00. Immediately below him: 921 runs, a strike rate of 206.50, 68 sixes — Abhishek Sharma. Third: 895 runs, 78 sixes, a strike rate of 184.91 — Karanveer Singh. Country: Austria.

The first question is the most uncomfortable one. Are these three numbers even comparable? That Kishan is the only batter to pass 1,000 international T20 runs this year is the clearest fact in the dataset. But the 206.50 strike rate beside it, and an Austrian player's 78 sixes — these are not the same currency. One list, with two currencies inside it.

The headline asks who made life difficult for bowlers. The evidence needed to prove it contains not a single bowling economy figure. One side of the ledger carries batting runs; the other side is a blank page for the bowlers.

From 53 years of watching the game and working inside its economics, one thing holds: a run chart is never the map of a match. It is the market's mirror, showing what we want to see. This year's mirror is glossy, colourful, full of sixes. Put your hand behind it and you find two kinds of paper: international T20, and all T20. Tear them together and the headline you get is not information — it is compilation.

The calendar matters here. The Pakistan–Sri Lanka series has finished; the India–West Indies series is still running. These are near-final aggregates, not mid-season figures. The hook used is the last Pakistan–Sri Lanka match: a fifty by Sahibzada Farhan and an 87 by Kusal Mendis. One match, two innings.

Extrapolating a season from one match is dangerous — and it is exactly what such pieces do most easily, because a single-match flash stays in memory while season-long subtlety does not. Mendis's 87 is remembered; how many times he fell for 35 is not. That is the first crack.

The second crack is larger. The rules on international T20 status changed in 2026, when the ICC granted full T20I status to all Members. So an international run list can now seat India's premier number three beside an Austrian player. The same word — international — appears before both names, but the opposition quality is worlds apart.

I have written before about how home-win rates fell when stadiums went quiet, because then I had data, explanation and a counter-question. Here the counter-question is simple: 895 runs against whom? 1,122 against whom? Put the two numbers side by side and the list becomes a paper calculation.

Ishan Kishan: controlled aggression. 32 innings, 1,122 runs, average 38.68, strike rate 170. Read together, these produce a specific profile. Kishan did not merely hit — he held and then hit. Batting at number three at a strike rate of 170 means he both anchored the innings and accelerated it. He is the year's only 1,000-run batter.

Abhishek Sharma: the inverse profile, the inverse risk. 921 runs in 32 matches, strike rate 206.50, 68 sixes — but an average of just 29.70. Read separately, these mislead. A strike rate above 200 with an average under 30 is a profile of impact, not consistency. Such a batter swings matches and also departs quickly. Ranking only by runs hides this entirely.

Sahibzada Farhan: the opposite pole. 697 runs in 15 innings, average 49.78 — the highest average in the group. But the lowest strike rate among the top run-scorers. Where others attack, he assures. Pakistan's batting structure rests on one steady anchor; India fields two or three aggressors at once.

Harry Brook: the most balanced signal. 690 runs in 18 matches, average 49.28, strike rate 189.04. Nearly Farhan's average, with a strike rate second only to Abhishek. Holding those two numbers together is the clearest signal in the dataset — a batter who can both anchor and accelerate. That is the modern T20 product.

Karanveer Singh: the biggest trap. 895 runs in 24 innings, average 42.61, strike rate 184.91, 78 sixes — top of the six-hitting list. But this is the paper calculation. Austria is an Associate Member; a large share of that aggregate came against weaker bowling. Placing him beside India and England data means writing two different exams into one ledger.

Place these five side by side and one thing is clear: this is not one kind of batter's list. It is at least four kinds — the steady anchor (Farhan), the controlled aggressor (Kishan), the high-variance power hitter (Abhishek), the balanced all-rounder (Brook), and the uneven-competition outlier (Karanveer). Ranked by runs, they form one list; ranked by role, four.

The second objection is what the list omits: phase splits. These are season aggregates. Who scored in the powerplay, who at the death, who held the middle — none of it is separated, yet the real T20 battle is fought over phases. A death-over specialist and a powerplay finisher do not carry the same 500 runs.

The third objection is the most uncomfortable, because it undermines the headline itself. The headline speaks of bowlers suffering. Yet no bowler's economy, strike rate or wickets appear. In a season of such scoring, what the bowlers actually did is not asked. Half a picture supports a whole claim.

Now the second ledger — all T20, adding franchise and league cricket. The biggest receipt is here. Ishan Kishan's 1,122 jumps to 1,724 with leagues included: roughly two-thirds of his annual T20 volume comes from franchise cricket. One number to the next reveals the real economy of modern T20.

Below him: Mitchell Marsh (1,544), then Jos Buttler, Tim Seifert, Luan-Dre Pretorius. These names together sketch a labour market — effectively year-round T20 professionals. The national shirt is one part of the work, the league shirt another, and most of the year is spent travelling and playing franchise fixtures.

The six-hitting list tells the same story: Abhishek 111, Dewald Brevis 101, Finn Allen 101. This is a franchise-heavy list. The real six-hitting factory is now the league, not the bilateral series. Where there are more matches and the opposition changes daily, there are more sixes. That is a fixture-design outcome, not a batting-talent statement.

An older receipt puts this year's headline in place. In 2026, Mohammad Rizwan scored 1,326 international T20 runs at an average of 73.66 and a strike rate above 134. This year's leading scorer, Kishan, is well below that. So this year's 'record' is only a record within this year — not an all-time mark. If the headline says record, it is a record with limited liability.

Another absence stands out. The outlet that compiled the list is Bangladeshi, yet no Bangladeshi batter appears in the top five — not in internationals, not in all T20 either. That is not a one-match matter. If, across several seasons, not one batter from a country reaches this height, it is a structural question, not a talent gap.

Where could I be wrong?

First, I assume the two ledgers should be kept apart. Some will argue the boundary between national and league cricket has already dissolved, so the very idea of separate ledgers is outdated. That is reasonable. But the question is not separation — it is labelling. Blending two sources into one number hides where the runs came from, and without that you cannot manage workload, rest or selection.

Second, I may be underrating Associate batters. Karanveer's 78 sixes are not casually dismissed. The issue is not his skill but editorial selection. If a headline claims 'international T20', keeping two tiers of data together is not honest. Otherwise the list gives not information but confusion.

Third, I am myself exposed to a seasonal temptation — seeing batting runs and declaring that bowlers have failed and pitches belong to batters. The bowling data that would settle it is absent. I once went to Russia looking for a match and came back with a receipt; that habit still applies — you cannot rule on what you have not seen.

Fourth, this list cannot judge match quality. No home-away splits, no pitch type, no dew, no DLS. In such an unqualified environment, the list can only reveal a trend, not deliver a verdict.

So what stands? Do not tear the paper; seat the two ledgers apart. Once separated, one truth becomes clear: this year's T20 batting boom is really a league boom, and the league boom is really a fixture boom. National series are only part of it.

A second truth: modern T20 batting success is now fitness-management success. Those at the top of the all-T20 list play the most matches, travel the most, and therefore carry the most injury risk. Yet this article mentions neither injury nor rest. In writing about a run boom, the biggest risk has been left outside the frame.

Why these gaps form is worth saying. Easy numbers sell; hard context does not. '921 runs, strike rate 206' becomes a headline. 'How many of those 921, against whom, in which phase, off which fixture' does not. So the paper calculation advances and the full calculation lags.

I am not talking about budgets, but about labour. A T20 batter's year now splits three ways: national duty, leagues, and conditioning camps. Add the three and you see why the injury list and the run list fill with the same names. Those names play the most, and so tire the most.

No one keeps that fatigue ledger, because fatigue cannot be sold. Sixes sell; strike rates sell. Medical confidentiality and club interest combine so that injury news surfaces in a form that suits the balance sheet. So whether a batter with 1,724 runs is physically sound is something the audience cannot know.

A related point: T20 live data now flows ball by ball straight to betting markets. Beside every shot sits a number that links the game to wagering. This list is compiled in the name of a batting festival, while a parallel calculation runs alongside it that never becomes a headline.

Finally, the forward question. Next year this list will not look the same. Three predictions. First, the all-T20 list will gradually become the primary list, and the international-only list will settle as a sub-list, because the numbers are already walking that way.

Second, the strike rate above 200 that is now written so easily will not hold as easily over the next two seasons, because opposition plans change fast and every side now uses phase-split data. Third, one of the year-round names will at some point be suddenly absent due to rest — and that will be the next big story.

So the headline's question — who made life difficult for bowlers — is answered not only in batting names but in accounting rules. Read the runs, but place beside them the opposition, the match type and the fixture load. Then a list becomes information. Otherwise it is only a mirror — glossy, colourful, and every time showing us our own reflection.