Marco Jansen's Double No.1 Is a Provisional Snapshot, Not a Verdict

At Newlands in Cape Town, Mitchell Starc was taking his sixth wicket of the Test, and in that same week the ICC's weekly rankings update landed. In it, Starc slipped one place in the Test bowling table, and Marco Jansen climbed to No.1 with 876 rating points — a five-place jump, plus the No.1 Test all-rounder slot alongside it. In one week, the fast bowler taking the most wickets on the field went down and the bowler who had taken five in an innings in his previous Test went up. Jansen's double No.1 is a photograph of a rolling formula, not a final cricketing verdict. The people publishing the table knew this: the Cape Town Test was still live, and the next update could reverse the picture.

A necessary disclosure first. Every figure in this piece comes from that single ICC weekly update, whose publication date is not recorded in the source. I have not cross-verified these numbers against a second source, so treat each as pending verification. What I cannot say: I do not have the ICC's underlying weighting algorithm or a match-by-match points breakdown. What I can speak to is how the ranking behaves — and it behaved exactly as it has for years.

Only three of nine top spots changed in this update. The other six did not move at all. That is itself a signal: the system does not swing quickly; it runs on a weighted window, and one or two innings give it direction, not character. So when three unrelated bilateral series — South Africa vs Australia Tests, India vs New Zealand T20Is, and an ODI tri-series in Pakistan — get folded into one 'rankings' frame, the reader's job becomes harder. Those three have zero competitive connection; the only thing joining them is the ICC's weekly cycle. Anyone building a 'momentum' narrative across them is committing a format-and-context error.

Now open Jansen's numbers. Ten wickets in two Tests, 5/33 in one innings, Australia bowled out for 99 at St George's Park in Gqeberha. With the bat, 146 runs across two Tests, including 85 at No.8 in one innings. That is genuine all-round output, no question. But the shape of it matters. Eighty-five at No.8 and eighty-five at No.6 are not the same commodity. Lower-order runs arrive when the team is already near 250-300 and the cost of risk is low; top-six all-rounder runs are what hold an innings upright. The 5/33 is also a single-innings event, not ten sessions of dominance. A left-arm seamer on a St George's Park surface against a right-hand-heavy Australian top order is a structurally favourable matchup — and that is my inference, not a stated fact in the source.

What does 876 mean? In Test bowling, a band around 900 is treated as the historical peak zone. 876 sits below it, which makes this a sign of approaching career peak, not of settling at the summit. The sample is two Tests, so hold confidence at medium — I will call him an emerging world-class quick, not the world's best fast bowler.

Temba Bavuma's case reads the same way. 179 runs, Player of the Match, and No.2 in Test batting. But the source gives no series aggregate, which means that No.2 rests on one innings. Reaching No.2 this late in a career is significant, yet South Africa's entire top-of-table footprint is concentrated in two men — Jansen and Bavuma. One quick, one batter. That concentration is fragility, not strength. A side whose ranking prestige rests on two players has a structure that can buckle on one injury. I think back to the Kolkata desk in 2026, when I built an Expected Runs Added model off 2026 IPL ball-by-ball data — the biggest lesson then was also that one player's inflated number tells you nothing about a team's depth.

Apply the same lens to Abhishek Sharma's return to No.1. Three innings: 29, 27, then 113 off 38 balls — a strike rate near 297. The elite T20I strike-rate benchmark sits above 150; 297 is a single-innings outlier, not a newly discovered capability. The ranking system rewards the outlier innings; team-selection logic cannot. The 29 and 27 before it suggest opponents had adjusted — slower balls and wide lines outside the powerplay, yorker lengths. In the third innings the high-risk method came off. That may be a technical problem solved, or one evening's coincidence. Three innings cannot settle it.

And here is the structural point that matters most in this whole update. The T20I batting No.1 has changed hands twice in recent months, once purely through injury. Ishan Kishan took it in July, was injured after one match, and the spot returned to Abhishek. A top ranking that flips on a single match's absence carries very little information about a player's true standing. That is a statement about the metric's stability.

Harry Brook's case is the cleanest format-specialisation illustration here. A 202 in the ODI tri-series in Pakistan, and still only No.8 in ODI batting — while he sits at No.1 in Test batting. His ODI appearance volume is too low for the ranking to catch up with his output. A 202 in an ODI is record territory for England, and the source handles it like a footnote. The real story is not the runs; it is the model's inadequacy.

For India, the biggest item in this update is not the one in the headline. Ravindra Jadeja losing the Test all-rounder No.1 — ending a reign longer than four years — is not merely a one-place slide. For more than four years he represented a role India's entire balance was built on: a spinner who bats in the top seven and bowls a full quota. That profile has no like-for-like replacement. And note, Jadeja fell one place — this is erosion, not collapse. Erosion is precisely the indicator that shows up before a selection transition.

Meanwhile India holds No.1 in ODI batting through Shubman Gill and in T20I batting through Abhishek. An asymmetry emerges: firm grip at the top of white-ball batting, loosening grip at the top of the red-ball all-rounder table.

Bangladesh's profile is the most honest mirror in this update. Highest Test batter 18th, highest Test bowler 18th, Mehidy Hasan Miraz third among Test all-rounders; best ODI position 24th; best T20I positions 23rd and one bowler at eighth. No top-10 specialist in any format except one all-rounder and one T20I bowler. That is not a talent shortage; it is a pipeline ceiling — players who contribute are being produced, match-defining specialists are not.

Now the part where I disagree with my own guild.

The strongest case for rankings is this: it is the only public, consistent, cross-format yardstick we have, and it weighs performance transparently. I accept that fully. The problem is not that the yardstick exists; it is treating it as a verdict. Three pieces of evidence sit right here. One: Starc dropped a place while taking six wickets the same week — the ranking trails performance, it does not forecast it. Two: Abhishek's No.1 returned on the back of a 297 strike-rate innings, after two scores under 30 — the model rewards extremes, not consistency. Three: that same No.1 has changed hands through injury. Correlation and causation are different things, and rankings measure correlation. I am not arguing for a contrarian verdict off two Tests or three T20Is — I am arguing that when the sample is small, uncertainty belongs in a full sentence, not a footnote.

And where the data agrees with the commentary box, say so plainly: at Gqeberha, Jansen genuinely was the difference. 5/33 and Australia bundled for 99 is a real, decisive event. I am not diminishing it. I am saying a single-innings event and a session-by-session status cannot both be measured by the same word, 'No.1'.

So what should you watch next? If Starc finishes the Cape Town Test with eight or nine wickets, Jansen's bowling No.1 can go back — and the headline will stay the same, only the direction will flip. The real question is not who is No.1 this week. It is whether the option India has prepared behind Jadeja matches that profile rather than that name. Rankings will change every Monday; structure does not.