Abhishek Sharma's 897 and Marco Jansen's 876: Counting the No.1 Spot, Innings by Innings

On Monday night Abhishek Sharma faced thirty-eight balls and made 113 — 2.97 runs per ball. On Wednesday morning those same thirty-eight balls became 897 points and returned him to the top line of the ICC T20I batting table. Second line: Sahibzada Farhan, 883. Fourteen points between first and second.

Third line: Ishan Kishan — thirty-one points back, two rungs down, and not a single ball faced all week. One table, two opposite directions. One batter climbed because he played; another fell because he did not. And the entire spread between them, thirty-one points or 3.5 per cent of 897, is narrower than the innings that settled the top spot.

I keep a field map for the moments the scoreboard forgets. In May 2026, sitting ten kilometres from the MCA ground in Pune, I re-plotted Rising Pune Supergiant's 128 for 8 over by over, because a one-run final had given me a result and no mechanism. The same habit writes this line: this week's rankings release is not a verdict, it is the output of a calculation, and that calculation runs in two directions at once.

The claim, in one sentence: the T20I No.1 tag is not a verdict on a batter but the residue of a small, decaying sample — and this week's table showed both halves of the machine together, one man climbing by scoring and another falling by not playing.

What the table actually measures

An ICC batting rating does not add career runs. It is a weighted average of points earned per innings across a rating period, with recent innings carrying more weight than older ones, and opposition strength sitting inside the multiplier. Three inputs therefore move any position: your new innings, the decay of your old ones, and everybody else's movement. Two of those three are not in your hands.

That is why a ranking should be read as a stock, not a flow. 'Abhishek returns to No.1' is a stock statement — a balance struck on one date. 'Abhishek made 113 against New Zealand' is a flow statement. The first is generated by the second, but they are not the same object, and newspapers merge them into one sentence so the reader believes he has read a performance.

Look at the shape of the table: 897, 883, roughly 866 — three batters inside a thirty-one-point band. A T20I opener faces twenty-five to forty balls an innings, so the entire top three is about as wide as one good knock. Asking that table who the better batter is happens to be the wrong question. The right one is: whose innings were the heaviest most recently, and whose calendar stayed busiest?

Here the format's rules of evidence need stating, because the next few paragraphs come from a table with a far bigger sample. Marco Jansen bowled across four innings in two Tests against Australia and took ten wickets — his Test rating rests on hundreds of deliveries. A T20I batting rating rests on a few hundred balls spread across a few dozen innings. The same points gap means different things in the two tables, so do not put Jansen's 876 and Abhishek's 897 on one scale. That is the error every weekly rankings roundup repeats.

Thirty-eight balls and fourteen points

Open the innings that decided the top spot. 113 off 38, a strike rate of 297.4. This was not an ordinary knock that nudged an average; it was an innings that dropped a large numerator into a small denominator. The arithmetic is plain: the fewer innings in your rating window, the more one innings is worth. T20I windows hold few innings — which is exactly what makes this format's rankings the most volatile of the three, and why the No.1 debate restarts every month.

Let me name my own variable's failure mode first. The 113 did not earn its points because of the size of the runs; it earned them because of the size of the denominator it entered. Had the same 113 come against a weakened attack in a dead rubber, the opposition multiplier and match weight would both have been smaller and the gain would have been smaller. So the movement cannot be read as proof of performance quality. It reads as a jump inside a sample. That distinction is the whole quality of the reporting.

There is a consequence the release does not print. The series is a five-match one and it is still running. The next innings can turn next Wednesday's table over again. Fourteen points is not a fortress; it is a pencil entry in a scorebook. A reader who files it as permanent status will collide with his own assumption within a week.

Ishan Kishan's fall is arithmetic, not form

The release says Kishan is injured, and does not say where the injury is sourced from. Here is the weakest link in release-driven reporting: the ranking numbers arrive from the ICC, the fitness claim arrives from a line in a newspaper, and both sit in the same paragraph without a marker between them. The reader has no way of checking which fact came through which door.

The arithmetic, though, is clear and does not depend on the injury at all. A batter who does not play keeps a fixed numerator while the weights on his older innings keep sliding; the men who do play push their averages up. He goes down. 'Kishan lost the spot' is the wrong sentence. 'Kishan's spot expired' is closer. Injury and rest produce an identical table, because neither involves a ball.

And this is where India's real selection problem enters, the one I call the squad budget. Abhishek, Kishan and Shreyas Iyer — three credible top-order roles for at most two slots. When three credible claimants chase one role, the price is set by scarcity, not by talent. The ranking table orders those three and creates the illusion that it has also resolved the selection. It has resolved nothing; role fit and the calendar will pick the XI, not the table.

The release also carries two Julys that readers skip past. One line says Kishan took No.1 from Abhishek 'in July this year'; another says Abhishek first reached No.1 'in July 2026'. Depending on the year of the release, those two Julys sit either one month apart or twelve. In a table that runs on decay, dates are not decoration, they are components. A report with blurred dates will produce blurred arithmetic.

Jansen's double: 146 runs, 10 wickets, 876 points

Marco Jansen jumped five places to No.1 in Test bowling on 876 points, and in the same week became No.1 in the Test all-rounder table. Two top spots, one series. The numbers: 26 and 35 in Durban, 85 in Gqeberha — 146 runs in three innings at 48.67. With the ball: 3/68 and 1/45 in the first Test, 5/33 and 1/34 in the second — ten wickets for 180 runs across four innings, an average of 18.00.

That is the mechanism of the all-rounder table. It adds two columns, batting points and bowling points. When both columns move in the same series, the combined table produces a large jump; and because the bowling column alone was high enough, it also reached the top of a separate table. Jansen did not win two tables. He played one series, and that series spread across two ledgers. Reporting usually flips this into 'two wins, one man', when the honest version is 'one series, two accounts'.

And that is how Ravindra Jadeja's reign of more than four years ended. Read the sentence carefully: Jansen has won the spot, no argument. It is also true that Jadeja did not defend it, because there is only one way to defend a ranking — play. The all-rounder table rewards players whose two columns keep moving; a thin calendar leaves one column or both empty. The reign was not broken, it ran out of time. Readers who see 'reign over' assume a sporting verdict; it was a scheduling one, at least in part.

I never write these shifts in the language of fate or form. In December 2026 the campus was shut and I was logging Adelaide's 36 all out ball by ball, by delivery type and by the batter's trigger movement, because 'a bad day' teaches nothing. The same rule holds for rankings: behind every fall there is a sequence — which innings is losing weight, which column went empty, who bowled how many overs in which week.

The top five, workload, and one useful insight

Look at the Test bowling top five: behind Jansen sit Mitchell Starc, Matt Henry, Ollie Robinson and Jasprit Bumrah. That list tells several stories, and the most useful is that all five run on different fixture diets. Australia's calendar is dense, New Zealand plays few Tests, England's season concentrates Robinson, and Bumrah's workload is managed. Which produces the insight I find most valuable in this entire release: the Test bowling table is less a quality index than an availability index. Whoever plays most climbs highest; a carefully managed bowler can hold a top-five place but rarely reaches the top.

That is a design feature, not a flaw. But it means presenting the ranking as testimony to greatness is a category error. Take Temba Bavuma: a Player of the Match performance lifted him four places to No.2 in Test batting. The award reads one match; the ranking reads a window. Two different instruments, and merging them into one paragraph is precisely the mistake I try not to make. A player can be the hero of a match and sit three places below a man who won nothing.

India's side of the release is counted too — Shreyas Iyer and Travis Head appear among the movers, under a line about 'plenty of other big movers'. My complaint is that the line promises and does not deliver: when you write 'plenty of other movers' and withhold the names and numbers, the reader loses the only thing worth checking — which column moved, how far, in which direction.

Contrarian: the release's language, and my own blind spot

The ICC's language turns this arithmetic into celebration — 'makes waves', 'double delight'. That is not wrong, it is merchandising. The rankings are the ICC's product and the release is its advertising. The problem starts when we mistake the advertisement for the news and fill the space where calculation belongs with theatre: 'returns', 'lights up', 'reign ends'. What that language drops is this: the story of the week is not that Abhishek returned to No.1. It is that one innings outweighed eleven months of everybody else's accumulation. You do not need a dressing-room source for that sentence; you need the table and its denominator.

My own method has the same blind spot waiting in it. Isolating one variable feels good, and isolation flatters the writer into believing a single metric is the whole causal story. The thirty-one-point band genuinely shows the summit is narrow — but if I carry it to 'the rankings are meaningless', I become wrong. The table is not meaningless. It answers a different question: who stayed available, and who produced the heaviest recent innings. That question is not worthless. It is simply not the question we keep asking it.

And the thing the release leaves out tells you the most. No series score, no match result, no state of the Test series. That is not carelessness, it is the nature of the instrument: batting and bowling ratings do not know who won the match. A 113 in a losing cause earns exactly what a 113 in a win earns. A reader who picks up the table believing it is a performance verdict is asking a gauge for a reading it was never built to give.

This is where I have to be most careful, because it is easy to stop at 'the rankings are hollow'. They are not. They are a cheap, weekly, genuinely useful indicator — provided you read them as an availability index and not as a talent verdict. The spreadsheet was not the answer; it was the first question with cells. This table is that too: the first question, not the last word.

Three checks for the next six months

My habit is to date a forecast and leave it checkable, because no model in this sport travels honestly past six months. Check one: Abhishek's next two innings in India's ongoing five-match T20I series. If he bats, the next two Wednesday tables either harden his 897 or bring Farhan's 883 to the top. Fourteen points can close in two innings, which is the most honest thing about it — and the reason this release should not be read as a career turning point.

Check two: Jansen's next six months of Test cricket. If his calendar thins out, the all-rounder summit will not stay with him, because that table demands two columns and empty columns do not score. Check three is the cheapest of all: any Wednesday, read the top three lines of the T20I batting table and ask whether the gap between them has grown wider than one innings. The day that gap outgrows a single knock, the table will have started looking past its sample.

Until then, keep this week's two numbers — 897 and 876. One tells you what thirty-eight balls can do; the other tells you what four innings can do. And sitting between them is the third number nobody headlined: 31, the margin that sent a batter two rungs down without a ball bowled. If the table cannot even tell us who won the match, why do we keep asking it to rank the men?