A 14-Point No.1: Abhishek Sharma's Return, Marco Jansen's Double, and the Part of the ICC Rankings Nobody Prints

The Ledger and Three Figures

In my hand-kept ledger, one name changed at the top of the T20I batting table this week. The man who was first is now third; the man who was third is first again. The event behind the swap is a single innings: 113 off 38 balls, a strike rate of 297.4, or 2.97 runs per ball.

The table reads: Abhishek Sharma 897 (No.1), Sahibzada Farhan 883 (No.2), Ishan Kishan 866 (No.3). The full spread across the top three is 31 points. First to second is 14 points, which is 1.56 per cent. First to third is 3.46 per cent.

The second story came from the Test table. Marco Jansen is now No.1 among Test bowlers and No.1 among Test all-rounders, on 876 points after a five-place jump, ending Ravindra Jadeja's reign of more than four years. Temba Bavuma climbed four places to No.2 among Test batters.

Both stories are true and both deserve to be printed. My argument is with the third thing no release prints, and the reason these stories will be stale by next week while the question underneath them will not: what is this ranking actually measuring, and is 14 points large or small against the thing it is being used to prove?

A Table, Not a Verdict

The ICC rating is a weighted average, not a total. A batter's points come from innings; a bowler's from wickets and their cost; an all-rounder's from both. Every innings does not carry equal weight — recent innings press harder, and any single innings is capped in its influence. The table updates weekly and is not permanent: when a series closes, new innings enter the window, old ones slide back, and the average recalculates.

One clarification matters, because the arithmetic ahead rests on it. The ICC ranking does not answer "who is the best player"; it answers "whose weighted average is highest given the recent innings that qualify." Those two questions usually give the same answer. They are not obliged to.

The raw material this week: Abhishek's 113 came on Monday against New Zealand in an ongoing five-match T20I series. Kishan took the top spot from him in July and is currently reported injured. On the other side, South Africa's two-Test series against Australia is live, and Jansen produced a series-shaping contribution with bat and ball in Durban and Gqeberha, where Bavuma was named Player of the Match.

Seventeen years in this trade have given me one habit I call the noise file: crowd, dew, travel, toss, and now availability. When a number surprises me, my first instinct is not to attach a story to it but to hunt the variable I forgot to count. In 2026 I hand-coded 1,842 deliveries of Delhi's Ranji season at the Feroz Shah Kotla — batter, bowler, line, length, shot, false shot. That sheet taught me that "bowled well" is an opinion and "14 false shots in 42 balls" is a fact. This piece is written under the same discipline: clean the table first, form the view second.

Thirty-Eight Balls, 113 Runs, and One Dumb Question

Start with the dumbest available check, the one that earns its keep. Is this innings as large as it looks?

113 off 38. A par strike rate of 135 across those same 38 balls — a rough benchmark for top-order T20I batting in recent series — produces 51. The innings sits roughly 62 runs above that par. There is a second way to see it: to reach 113, even in the most six-heavy arithmetic possible, at least 19 balls must have been hit for six. Half the innings, at minimum, was spent on the boundary. The real ratio would have been higher, since fours and running replace sixes.

Against par, this innings runs at roughly twice the going rate, and that single figure is what earns it a place in the No.1 argument.

Now the part the release does not supply. What was the pitch? How many runs came in the powerplay? Which attack was in front of him? Was it a small ground? I have none of those four variables. So "62 above par" is suggestive, not confirmed. The distinction matters, because par comparison without condition adjustment is the same error I made in 2026, when I logged every shot of the World Cup and had France at 10.4 tournament xG against 14 goals actually scored. The lesson was clean — finishing is noise, chance creation is signal — and its cricket translation was that I stopped quoting run rates alone and started attaching a baseline to every number I published. If a figure has no "against" behind it, it does not run in my column.

What is certain about Abhishek: 113 off 38, a strike rate of 297.4, and a return to No.1. What is not certain: that this innings makes him the best T20I batter in the world. The ranking itself does not say so.

The Fourteen-Point Gap

The number the whole story hangs on is 14.

Fourteen points between 897 and 883 is 1.56 per cent. In a weighted-average system, a good innings typically moves a rating by double digits — that is my estimate, not a published ICC rule, and I will file it as suggestive. If it holds, the conclusion follows: the gap between first and second sits inside the range a single series, or a single innings, can close. The top spot is conditional, not fixed.

There is a second edge to this. Farhan is 14 points behind and his name barely appears in Indian coverage. That is a coverage failure, not a ranking failure. A player within 14 points of No.1 belongs in the same sentence as No.1, or we end up printing "No.1" as a trophy while deleting the race that produced it.

Kishan: A Frozen Number

Ishan Kishan was No.1 in July. He is third now, 31 points behind. The release mentions an injury and supplies no team source, no medical confirmation, no date. Professional honesty requires filing that with every other unattributed claim: working, unverified.

The mechanism underneath is the least understood feature of weighted averages. Injury does not deduct points. When a player stops playing, his old innings stay where they are and his rating stands still. Everyone else keeps batting, adds innings, and passes the frozen number.

Injury does not take points off a ranking; it takes time away from the points.

It is the suspended-stock problem: the price does not fall, it simply stops moving while the market moves around it. Kishan's 866 did not drop; it held while Farhan's climbed. Suggestive, again, because the ICC does not publish which innings entered or left the window this week.

The cricket consequence is that India's opening debate is no longer a form debate. It is an availability debate, and the distance between Abhishek, Kishan and Shreyas Iyer looks smaller on the rankings page than it will on a selection sheet.

Jansen's Double, and Jadeja's Empty Calendar

To the Test table. Jansen's numbers come from a two-Test series, and I added them up — the sum no release performs.

Batting: 26 and 35 in Durban, 85 in Gqeberha. That is 146 runs in three innings, an average of 48.67. Bowling: 3/68 and 1/45 in the first Test, 5/33 and 1/34 in the second. Ten wickets at 180 runs, an average of 18.00.

His second Test reads 85 runs and 6/67 — the kind of double that belongs at the top of an all-rounder table rather than the kind where one discipline carries the other.

Run the dumb check: batting average divided by bowling average. 48.67 over 18.00 is 2.70. No model, no expected-runs framework, no borrowed football vocabulary. Two numbers divided. It says Jansen was roughly equally ascendant in both departments across this series. Models are for when the scorecard refuses to answer; here the scorecard answered.

A caveat, filed on purpose: three innings and four bowling innings is a small sample. Calling anyone the world's best all-rounder off one series is the same hurry as calling the weather off one afternoon. The arithmetic is confirmed; the verdict is conditional.

Then Jadeja. More than four years at the top, ended. The easy story writes itself — Jadeja declined. I have no evidence for that. What I have is a different question: what was his rating built on, and how many new innings arrived to refresh it? India's Test calendar, his role, his availability — those three variables move that number as surely as his bowling does. The claim is unresolved because I do not have his innings-level inputs. It is also exactly where a ranking stops being a story and becomes a schedule.

Kishan slipping to third and Jadeja losing the top are not two stories from two formats; they are outputs of one mechanism: a weighted average does not punish the player who does not play, it forgets him.

Five Countries, Five Seamers

Jansen's 876 points and five-place jump put him first. The top five also includes Mitchell Starc, Matt Henry, Ollie Robinson and Jasprit Bumrah. I am deliberately not ordering them, because the release does not and I do not print order I have inferred.

What is visible: every place in this week's top five of Test bowling belongs to a seamer from a different country. South Africa, Australia, New Zealand, England, India. No spinner.

That says something real about the red-ball game: elite capacity is not concentrated in one country or one bowling culture. It does not say spin is dead — a weighted average rewards volume and cost, and spinners get fewer qualifying bowling innings in a home-summer calendar. Still, this is what the table says this week, and I am writing about the table.

Bavuma, and the Award the Ranking Cannot See

Bavuma climbed four spots to No.2 among Test batters after his Player of the Match innings in Gqeberha. A small, clean point belongs here.

The ranking does not know a Player of the Match award exists. It knows runs, and it knows which innings the runs came in and how heavily to weight them. Awards are a journalistic instrument, not a rating input. Folding the two into one sentence is convenient and misleading — if awards paid points, Bavuma would have climbed more than four, and Jansen's 85 and 6/67 would have entered the same arithmetic.

What the Release Leaves Out

The release says several other big names moved — Shreyas Iyer, Travis Head among them — and gives no points for them. That is an incomplete record. A rankings story that names movers without their numbers is a press release, not a dataset. The reader cannot check it, only accept it.

The second omission is dating. The release says Kishan took No.1 in "July this year" and that Abhishek first reached No.1 in "July of 2026." Two Julys, one year, no explicit link. That small mess blurs the whole timeline, and the release carries no publication date at all.

A number is only as honest as the person who typed it. When the date is ambiguous, clean arithmetic buys you nothing.

This is where my 2026 file comes back. The IPL in the UAE, three grounds, nobody in them. Coding all 60 matches, I found death-overs economy up roughly 0.6 an over on 2026. In December, India were bowled out for 36 in Adelaide. Thirty-six runs, and every column I trusted went quiet at once. I spent four weeks re-watching every ball before writing a word. The lesson was not to make the story bigger. It was to make the sample bigger.

No.1 in the Commentary Box

One front the data desk settled years ago and has still not won: broadcast.

Somewhere on air this week, "world No.1" will arrive in three words. It will not carry 14 points, or 883, or 866. The truck has all three numbers. By the time they reach the microphone they have become an adjective. My complaint is not that commentary is emotional — emotion is the job. My complaint is that calling a 14-point margin "the best in the world" is a claim the number itself declines to make.

The same audit applies harder to the women's game. After the 2026 home World Cup and the WPL, coverage has boomed without a statistical backbone. In the men's game I can argue about 14 points; in the women's game I am often handed no innings-level baseline to argue with. The legacy test is collection, not sentiment.

Correlation, Not Causation

Now the part where I have to argue with my own brand.

Counter-intuition is the beat, and beats calcify into tics. A tic hunts for inversion in places where the straight reading is correct. So print the boring finding first: Abhishek Sharma is in the hottest T20I form in the world right now, and the 297.4 strike rate proves it. Inverting that would be dishonest.

The contrarian claim is narrower. Movement in position is not movement in ability. Returning to 897 does not say Abhishek became a better batter overnight. It says his new innings slotted in as an old one lost weight, and Kishan's innings slid out of the window. Part of this is a denominator story, not a numerator one. I file it as suggestive, not confirmed, because the ICC does not publish innings-level weights.

The Jansen-Jadeja case makes the distinction sharper. Jadeja losing the top is not proof of decline; it may be proof of a calendar that stopped supplying qualifying innings. Unresolved, and printed as unresolved. Jansen, by contrast, earned his place from both departments, so his No.1 is not a window artefact. One mechanism explains both outcomes, and that mechanism is arithmetic, not politics.

One uncomfortable addition. The ICC is the authority on its own rankings and their marketer. Both roles are real and they travel together. When a release reaches for "double delight" and "makes waves," that is promotion, not reporting. My job is to strip the adjectives and keep the numbers, trusting that the reader does more with a figure than with a flourish.

What to Watch

There is no conclusion here, only a watchlist.

The biggest threat to Abhishek's No.1 is not a rival's innings. It is a washed-out match and no new innings at all — in a weighted average, an innings that never happens is still an event. Farhan sits 14 points back and his next score can turn the table over. Kishan's return and fitness will answer what 866 really was: form, or a freeze.

Jansen's double holds only while his bowling innings keep arriving against Australia. The all-rounder table averages two departments, so one bad match damages from both sides — the fastest punishment in the rankings and the least discussed condition.

And one thing I will ask my desk for this year: publish the innings-level inputs alongside the table. I do not need the ICC to open its algorithm. I need to be able to check where 14 points came from and where 31 went. When the row changes again next Wednesday, the question should not be who is No.1. It should be how many innings sit behind that number, on what pitch, against what bowling. The day that question becomes part of the reporting, the rankings stop being news and start being evidence.

I kept the ledger by hand until the numbers started talking back. I did not find the pattern; it waited for me to finish counting. The counting is done, and the next count starts on Wednesday.