ICC Rankings Update: Marco Jansen Tops Test Bowling and Allrounder Charts, Abhishek Sharma Returns to No. 1 in T20I Batting

At 6.40 on a Mumbai morning the two monitors in my Andheri flat were still dark and I was opening the ICC rankings table on my phone. This is the table that changes without a press conference. Nobody did anything overnight, no coach issued a statement, no board sent a circular — and yet one name climbed and one slipped. This week Marco Jansen's name sat at the top of two separate columns: Test bowling and Test allrounder. Ten wickets across two Tests, a 5/33 in one innings, and 85 runs batting at No. 8. On the other side of the ledger, Abhishek Sharma, whose 113 off 38 balls put him back on the No. 1 chair in T20I batting.

I have kept a hand-written spreadsheet since 2026. At that first Indian Women's League in Cuttack I called thirteen matches in eleven days from a plastic chair beside the touchline and paid a local statistician ₹4,000 out of my own fee so the shot charts would keep coming. The final was played before a few hundred people and the channel's YouTube stream peaked at 2,100 concurrent viewers, a number I still quote in meetings. That sheet logs every player's minutes, position and club. The ICC table is the same habit at industrial scale, except the formula is hidden in the machinery and almost nobody reads the formula.

This week's update is clean and dense. Beyond Jansen, Temba Bavuma's 179 pushes him up the batting list, Harry Brook and Scott Boland have moved north, Simon Harmer appears with a gain, Shaheen Shah Afridi has climbed for Pakistan and Azmatullah Omarzai for Afghanistan. Mitchell Starc, Matt Henry, Ollie Robinson, Jasprit Bumrah and Ravindra Jadeja continue to circulate in the upper reaches of the same table. That is the strength of this kind of roundup — geographic and format spread. It is also the weakness.

When Test, ODI and T20I rankings travel in a single report, a reader's three scales merge. A captain's name that rose in one format and fell in another ends up in the same sentence. I spent fifteen years in broadcast production and learned one thing: any spreadsheet in which three different scales are coloured into one chart eventually deceives somebody. The same caution applies here.

The real question is what the numbers are built on. In Test bowling, every wicket is not worth the same. The rating of the batter at the other end, and his position in the order — top or tail — together decide the points a wicket carries. A top-order wicket carries more weight, a tail-ender's less. In batting, runs, the match situation and the quality of the opposing attack all enter the calculation, which is why the same 85 against a weak attack and against a strong one do not earn identical points. And the allrounder ranking is almost directly a function of the batting and bowling ratings — less a separate computation, more a sum of the two columns.

Jansen's case is interesting precisely because he filled both columns at once. Eighty-five at No. 8 delivers the batting bump usually reserved for the top order, because a lower-order batter gets fewer innings and fewer long innings — and a long innings is the single biggest condition for a batting rating. Add ten wickets in two Tests and a 5/33, and you get the exact combination that opens the top of the allrounder table. A player who bats at four and bowls four overs a month cannot reach that chair arithmetically, whatever his reputation.

Abhishek's return runs on the opposite arithmetic. The base of a T20I batting rating is narrow — short innings, limited balls — so a single innings carries enormous weight. One hundred and thirteen off 38 balls is nearly three runs a ball. Folded into an average, that produces a sharp upward jolt. His two previous innings in the sequence were 29 and 27, so the strike-rate burst and the consistency do not yet line up — and that is the part such updates mention least.

One more thing needs logging, because roundups usually dispose of it in a clause: Ishan Kishan's injury. An injury is a selection circumstance, not a cause of a ranking. Abhishek's points came from his own innings, not from a teammate sitting out. Place the two in the same paragraph and a reader absorbs the idea that rankings arrive when someone else's chair empties. It is the smooth sentence that reads true and means something false.

This is where my oldest habit applies: documents first, story after. This update carries no date. It does not state the ranking period. It does not say which match weights and opposition strength coefficients produced the numbers. The 179, the ten wickets, the 5/33, the 113 off 38 — these are scorecard-derived figures and need separate verification. As a news brief it is adequate if the ICC update and the scorecards are checked together. As a source for deeper analysis it is thin, because it presents rankings as a reward and never opens the mechanism.

And here is what troubles me most about this table. A ranking is less a mirror of performance than a mirror of the calendar. The player who gets twelve Tests a year and the one who gets five are weighed on the same average-based scale, but their ratings live entirely different lives. For the player with fewer matches, one bad innings sits in the average for months because there are not enough new innings to wash it out. For the player with more matches, the same bad innings thins within a fortnight. That is not a difference in quality; it is a difference in opportunity — and it has no column anywhere in the table.

Second, the allrounder ranking has a structural softness I watch regularly. It demands a minimum qualification in both departments, but that threshold is low enough that occasionally a single tour lifts a player. Jansen's case is not an abuse of the rule — ten wickets and a big innings across two Tests is a genuinely rare combination — but understanding the list means knowing how quickly the chair can change hands. The speculation that the top two bowling spots could shift soon is speculation, not fact, and should be printed as such.

Third, and this is my own beat. The same weekly refresh publishes the women's ODI and T20I tables. Not one of those columns appears in the roundup. I am not alleging anyone dropped it deliberately; I am recording that a document available every week is also overlooked every week. In 2026, when the league's final rounds were cancelled three days before kickoff and I drove back from Navi Mumbai with an empty notebook, I started a Sunday call-in that reached forty players, many of whom had gone months without stipends. That experience taught me that the name missing from the table can be the table's biggest story.

Fourth, the No. 1 T20I batting crown is the most fragile crown in the sport. The reason is plain: limited balls, limited innings, and a heavy strike-rate influence. One evening's explosion can lift you; the next two evenings can bring you down. That is not weakness, it is the nature of the format — but when a news report writes "takes back the crown", it should also say when that crown last left, in which update, and by how many points. That record is not in this update. Available information suggests Ishan Kishan overtook Abhishek in July, but justifying the word "back" requires the full prior sequence, which is absent.

Here I have to face my own worst instinct — the comfort of hindsight. Reading any rankings report, it is easy to conclude that whoever rose was always going to rise. If 113 off 38 looks inevitable today, remember that nobody calling that innings knew it would move a ranking. I have sat at matches where the scorecard at half-time said one thing and the final whistle said another. The table comes later; the match happens first.

There is another aspect of this update I keep underlining: among the names, Bavuma's 179 is the largest individual figure, yet it sits in the second tier of the news because no "number one" badge attaches to it. That is the selection logic of journalism — we report the rank, not the innings. For me the story is always the twelfth name on the sheet, not the first. In this update the twelfth name is the bowler who took two wickets, quietly slipped two places, and will be remembered by nobody.

As for the India–New Zealand T20I series and the ODI tri-series in Pakistan and the UAE, they appear here only as context. That lets a reader assume the rankings are the product of these series, when technically a ranking is a continuous calculation in which older matches retain weight. The distinction looks small and is not.

I once rewrote an opening script four times because a senior producer frowned at the first read. Today I regard that as my worst habit. So this time I will stop at one thesis: this update tells you who reached the top, and not how durable the top is — and durability is what real analysis rests on.

What to watch is that the third Test is still running and the table will move again at the next refresh. My eye will not be on the first row but on the column beside it that records how many matches a player has played. The day readers start reading that column too, rankings journalism will change.

What remains unverified: the exact date of the rankings update, the calculation period, and the current status of the injured player all require confirmation from a primary source. What is being treated as this update's biggest story is, in substance, a table refreshing itself. The question is not who is on top. The question is which column put him there — and who is reading that column.