Abhishek Sharma Is No. 1, but Marco Jansen Is the Real Story

The wind at Sky Stadium in Wellington that evening was so strong that the stump mic picked up its whistle before the sound of bat on ball. I got that detail from a replay I watched three times on my second screen — the third T20 of a five-match series, and Abhishek Sharma had already made 113 off 38 balls. Two balls short of six full overs. A strike rate of 297.4. It was his fourth T20 international century, and India won by six wickets.

I have seen that 38-ball number before — always in the corner of some scoreboard, attached to a different name. And every time, someone in the commentary box has closed the conversation by calling it an “explosive innings.” The second screen taught me that every voice has a replay, but a replay is not the whole story. It happened again this time. The headlines made Abhishek number one. The story buried inside that Wednesday's rankings table belonged to a different name altogether — Marco Jansen.

In the latest ICC men's T20I batting rankings, Abhishek tops the list with 897 rating points. Pakistan's Sahibzada Farhan is second on 883, and Ishan Kishan has slipped to third on 866. The gap between the three is 31 points. This is the same Kishan who held the top spot in July, and who missed the second and third T20Is of this series through injury.

One basic thing needs settling first. This is the third match of a five-match bilateral series, not an ICC global event. Rotation and experimentation are legitimate in such fixtures — a team's strategy, not its emergency. Kishan sitting out should be read inside that frame, not as a punishment. In thirty-five years of touring with Indian teams, I have seen this repeatedly: a player being rested mid-series is never a cricket decision, it is always a calendar decision.

This one report has pulled four different worlds into a single breath — a T20I in Wellington, a World Test Championship match in Gqeberha, the women's ODI table and the women's T20I table. Each has its own rhythm and its own history. Reading them as one continuous sentence is the oldest habit of my profession, and the most expensive one for the reader.

Back to the innings. Thirty-eight balls is six full overs minus two deliveries — the entire powerplay (36 balls) plus two balls of the seventh over. Only two fielders can be outside the circle in that phase. Abhishek's hundred is essentially a hundred built inside the powerplay; that is a different skill category, not the general category of a “fast hundred.” A hundred off 60 balls is built against a spread field, where the batter has to find gaps and hold the shot back; a hundred off 38 is an exploitation of fielding restrictions. Putting both in the same drawer is the most common analytical error in the game.

A strike rate of 297.4 sits outside every benchmark. An elite T20 opener's career strike rate is roughly 140 to 155; even in the powerplay, the best sit around 155 to 175. This innings is nearly double that. 297.4 is a ceiling demonstration, not a mean expectation; any claim that it is repeatable comes from enthusiasm, not from data.

Wellington's wind cannot be excluded from that arithmetic. The ground is known for strong, gusting wind that distorts swing, ball flight and a bowler's run-up rhythm. The wind is a commentator too — it just needs a stump mic. In such conditions bowlers cannot hold their lines, and a batter's cross-batted and lofted options yield more than their share. The original report did not mention the factor at all. There is no reference anywhere to dew, Duckworth-Lewis or a weather interruption, so I will draw no conclusion on that side.

What is far more durable than 113 off 38 is the count of four T20I centuries. Four hundreds are solid evidence; one 38-ball hundred is volatile evidence. Scoring hundreds across different tours and conditions is a genuine marker of skill; a one-evening strike rate of 297.4 only tells you where the ceiling sits. Nor is the result as clean as six wickets sounds — the target, the overs remaining and the fall of wickets are all unstated. A six-wicket win can be a cruise with four overs to spare or a last-over scramble. I do not have enough ground to say India dominated.

The arithmetic of the rankings matters here, because that is where the biggest misunderstanding is born. ICC player rankings are a weighted average, with recent performances weighted more heavily and older ones decaying. The key point is that a player's rating does not fall because he does not play; it stays where it is. Ishan Kishan's points did not drop — he was overtaken. The sentence saying he “fell to third after missing the second and third T20Is” is an optical illusion, not a methodological one. Abhishek climbed to 897 and Farhan to 883, and the ladder moved under Kishan's feet.

A top three spread across 31 points, with a gap of only 14 to second place — that is not a throne, it is a snapshot. One ordinary innings or one poor match can reorder it. Treating “world No. 1” as an established status and writing three paragraphs on it is the most common over-reading of data in our trade.

Now the story that got no headline. After the Gqeberha Test, Marco Jansen stands first in the Test bowling rankings and first in the Test all-rounder rankings at the same time. In that same match he added 85 runs with the bat and climbed thirteen places to 56th in the batting table. A left-arm fast bowler who also scores Test runs occupies the thinnest positional category in cricket; topping two tables simultaneously is the rarest event in this entire report, and the least read. The all-rounder table rewards dual output while the bowling table rewards specialism — winning both means clearing two different standards at once.

Jasprit Bumrah has slipped to fifth on 853 points. Do not read that as decline. Fifth place on 853 points tells you the top of the Test bowling table is extremely compressed — a one-place move is noise, not signal. For a bowler on a managed workload, ranking movement is at least as much a fixture-count artefact as a form signal. Mitchell Starc is second, down one — that is the arithmetic of Australia's ageing pace core, not the story of a single evening.

Ravindra Jadeja has lost the all-rounder's top spot after more than four years. That is not a statistic, it is an end-of-era marker, and it deserves the seriousness we reserve for a retirement announcement.

Shreyas Iyer is ninth on 758 points, down five — in the same sentence that calls him India's T20 captain. A gap of 139 points to the top is a quiet contradiction between the status of captaincy and the status of a ranking, and it should be exposed rather than smoothed over.

In the women's tables, Laura Wolvaardt has taken the No. 1 ODI spot with Smriti Mandhana second; in T20Is, Shafali Verma is third and Mandhana fourth. Two Indian openers sit in the top five, and that news earned no more than a paragraph that day. When I first sat down for a second-screen commentary feed seventeen years ago, I assumed voices were assigned from the top down. I know better now: voices are not recorded anywhere by default; they get recorded only on the day somebody writes them down.

Which brings me back to my oldest trap. A replay makes you feel you have the whole truth — 38 balls, 113 runs, case closed. But a replay is cut; the full sequence, the original commentary, the scorecard context and the match situation all need separate checking. The second-screen clip feels intimate, and therefore feels complete. That illusion is the most expensive one in my profession.

The second danger sits in the report's own architecture. Within fifteen lines a reader travels from a Wellington T20I to a Gqeberha Test to a women's ODI table. None of the three are comparable. A reader who absorbs “No. 1” as a single global status is being misled by format adjacency. A ranking is a photograph; the story usually lives outside the frame.

And one thing about Abhishek that demands honesty rather than sympathy. His ceiling is being established faster than his floor. A player whose headline number is a strike rate of 297.4 has, by definition, not yet shown what he does on a low-scoring, seaming pitch or under knockout pressure. The absence of any failure-mode data in this report is itself information.

Fourteen points. That is the distance between Abhishek and Farhan today, and it is also the reason to watch the remaining two T20Is closely. For me the biggest question is not Abhishek's next hundred but his next match in which two wickets have fallen inside the powerplay and the field is spread. And my other eye is on Gqeberha, to see whether Jansen's double reign is a season's product or the start of a long run. Memory is the one scoreboard nobody updates — and on that evening in Wellington, the first thing my ears recorded was the wind, not the runs.