ICC Rankings Update: Jansen's Double No.1, Abhishek Sharma's T20I Return — and the Date the Table Forgot

One player, one fortnight, two separate tables — and the top spot in both. Marco Jansen took ten wickets across two Tests, produced a 5/33, and in the same stretch made 85 from No. 8. When I stopped the scorecard frame by frame, the real story was not in the numbers but in the architecture of the tables: the bowling list and the allrounder list are different ledgers running on different currencies. One account was filled with the ball, the other with the bat. In the latest ICC rankings update Jansen sits top of both, and that is the most interesting thing about this report — because the innings that bought the allrounder crown came from No. 8, a position from which 85s do not normally arrive. The second anchor in the same update is Abhishek Sharma, back at No. 1 among T20I batters after 113 off 38 balls. The context is Ishan Kishan's injury, and the fact that Kishan had moved ahead of Abhishek in July — so the "takes back the crown" framing is technically fair, but how you read it matters. The supporting movement is broad: Temba Bavuma (179), Harry Brook, Scott Boland, Simon Harmer, Shaheen Shah Afridi and Azmatullah Omarzai — three formats and six countries, from South Africa to Afghanistan. That is good coverage, and it hides a specific risk: format blindness. Start with the mechanism, because reading a ranking as news and reading it as arithmetic are different jobs. ICC rankings run on a rolling window — every innings or match earns a score, and recent performances carry more weight than older ones. There is a minimum qualification threshold, so a player without enough innings or matches does not appear at all. The three formats run separate tables, and the allrounder table is a different kind of sum: it stitches a batting rating and a bowling rating into a single account against a fixed benchmark. I will be explicit that the fine print of the formula is not simply explained in public language, so I will argue from architecture rather than invent coefficients: where the points are added together, the meaning changes. That is why Jansen's double No. 1 is less a headline than a cost ledger. His entry in the bowling table was bought with ten wickets in two Tests and a 5/33 — the currency we all know how to count. His entry in the allrounder table was bought with 85 from No. 8, because that table adds the batting column separately. Standing top of both does not mean he did the same job twice; it means he did two different jobs at once and cleared the threshold that moves a table both times. The No. 8 score of 85 is worth recording precisely because No. 8 in Test cricket is historically a structural position rather than a batting position — a big score from there always signals something about the shape of the team, whether it is a strengthened tail or a top order that fell early and forced the shift. From years of watching matches, one thing I have noted: we count wickets, but the rankings do not count wickets — they count the price of wickets. A fast bowler's 5/33 on that pitch, in that weather, against that batting order, and another's 5/33 on a flat deck are not the same object, and the formula cannot fully capture the difference. So when someone says Jansen is now the best Test bowler in the world, my answer is: the table says his average is the highest. That is a measurement, not a verdict. The gap between the two is exactly what journalism should print, not hide. Now the Abhishek Sharma portion, where framing and arithmetic take different roads. 113 off 38 balls is a strike rate of roughly 297.4. Every headline will pick that number up, and rightly so. But a ranking does not move on one innings; it moves on accumulation. His three scores in this series — 29, 27 and 113 — push the table together, not the 113 alone. That detail matters because it tells the reader the ranking is a ledger, not a highlight reel. The second detail is that Ishan Kishan's injury is a selection context, not a computational cause. The injury created space in the news cycle; the points in the table come from runs. Collapsing the two is the most common error in rankings reporting: we treat the reason for the story and the reason for the table as the same thing. Look at the geographic spread in this update: Bavuma's 179 in Tests, Brook and Boland in the England and Australia Test contexts, Harmer from South Africa's spin depth, Shaheen and Omarzai in the ODI tri-series running across Pakistan and the UAE. That variety reads as good journalism, and it is — but it is also a trap for the reader. When Test, ODI and T20I numbers appear in the same paragraph, the mind starts weighing them on one scale. The three tables are three scales with different units, different match weightings and different historical depth. From my own experience I can say that when I first built a rankings-based grid in 2026 — borrowing the method I had taken from football — my biggest error was merging formats, and new readers make that error every week. There is one more thing this report did not touch, and to my mind it is the biggest clue in it. The table has no date on it. The original carries no publication date, no ranking period, no note of which match the update followed. A ranking is a freeze-frame, and a freeze-frame without a timestamp is not evidence; it is rumour. The Silence Tax is not empty air; it is a measured cost — and here the cost is credibility. When I watch a match from Sydney at 1 a.m., the score on screen runs with an over number, because I know a score without a time is useless. Rankings reporting routinely lacks that discipline. The second absence is heavier: the women's rankings. This entire roundup contains no woman player and no mention of a women's table. That is not an oversight, it is architecture — the roundup maps the same information pipeline in which men's cricket arrives first and everything else later. I have learned to count this: what is missing sometimes tells you more than what is present. Now the part that looks better when read from the opposite direction. The report does admit one thing most rankings copy hides — that the third Test is still live, so the top bowling spots could change quickly. That is an honest warning and it belonged at the top, not the bottom. A solid insight falls out of it: in a table where the gap at the summit is this narrow and the weighting leans recent, the table is not a certificate of "best" but an invoice for "the most heavily weighted recent performance." Jasprit Bumrah, Mitchell Starc, Matt Henry and Ollie Robinson sit in that cluster, and allrounders like Ravindra Jadeja are a recent reminder of how fast the table changes its mind. A good model does not shout; it waits for the third run — and so does the ranking, except we present it as shouting. The most useful part of this update is not what it states but what can be counted from it: three formats, six countries, one Jansen, one Abhishek, roughly sixteen data points. That is a strong factual density for a short report. My objection is not to the geography or the numbers; it is that the table's durability is never stated. If the third Test ends tomorrow, tomorrow's table will differ, and the reader will have no way to know which sentence is still true today and which became false overnight. I stole the grid once and paid for it with an A$80 byline — and the lesson was that a frame must be printed with its time attached. So how should this report be used? Read it as a snapshot, not a verdict. What holds is this: Jansen topping two tables is a genuine structural event, because he is the rare profile that pays in two currencies at once — new-ball wickets at the top, batting depth from the tail. Abhishek's return to No. 1 is also solid, but it is the product of accumulation, not one explosion. Names like Shaheen and Omarzai are moving in a different, ODI table, and keeping them separate from Test numbers is the reader's own responsibility. What does not hold is the dateless presentation. For me that became the real subject of the report — not Jansen's ten wickets or Abhishek's 38 balls, but the formal emptiness in which rankings are served as news. A ranking is a process; writing it as an event is convenient, because an event needs a date and a process needs a context. When we turn process into event, the context is cut and the headline survives. That transaction happens every week, and every week someone pays for it. The next step is clear and checkable. In the update after the third Test, watch whether Jansen holds the top spot — if he does, this was not a two-match spike. And in the India–New Zealand T20I series, watch whether Abhishek's No. 1 was the product of a vacated slot or of his own consistency. The ranking is real, but it is not an answer; it is a question that changes its answer every Monday. The truth is I will be at that screen again at 1 a.m., opening the same table, looking first for the date that should have been printed at the top.