37 Wickets, a Bowling Spreadsheet, and the One Fact Nobody Read

In a cramped old shop in Connaught Place in 2026, I used to feed ball-by-ball scorecards. Between Cronje's confession in April and Azharuddin's life ban in December that year, I pulled 11 seasons of one-day scorecards — 1,047 matches — built a “collapse index,” flagged eleven innings as anomalous, and watched two flags die under scrutiny. I retracted both in print, by name, in the same column. Since then I have had one habit: the first question I ask any number is which surface, which opposition, which match state produced it. Tanush Kotian's 37 wickets demands exactly that question, and this time the answer is hiding inside the very report everyone read and nobody lifted out.

The fact that should have been the centre of the debate

On Wednesday, day three of the Ranji Elite Group D match against Railways, Tanush Kotian took 7/45 — in the first innings, an innings-terminal haul, not a fourth-innings miracle. The report does not tell us the match state: follow-on, declaration, wickets tumbling or batters set. But what it does tell us is bigger. It came at Brabourne, which the writer himself frames as “closer to what's seen in home Tests — quicker, spinners can rush the batter.” Against that, the BKC surface where Kotian's career-best 11/151 came is described as a “typical slow turner.”

That single line is what the whole piece rests on, and the writer does not fully cash it. Anyone can dismiss figures from a slow turner by saying the pitch did the work. But his own report calls the Brabourne surface Test-representative — meaning 7/45 is not just a Ranji spell, it is a spell produced in the conditions closest to international cricket. The first rule of any data desk is: write the surface next to every number. A number without its surface is not data, it is advertising.

The real map of 37 wickets

Now the arithmetic. 37 wickets in seven first-class matches this season, spread across the Duleep Trophy, a match against Australia A, and the Ranji Trophy. In Ranji alone, 22 wickets in four games with the fourth still running — extrapolate that to a full season and you get 45-50, a very strong return for a frontline spinner in Indian domestic cricket, not an exceptional one. Season-best 8/81 against Haryana, career-best 11/151 at BKC. Two consecutive big hauls — 8/81 then 7/45 — the trend is sharply up, no doubt there.

I have spent years running numbers in transfer windows, and one thing I learned: a bowler's real value is not in his wicket count but in the mechanism by which he takes them. Kotian himself says his method is patience and pressure, forcing the batter into a rash shot, and two of his LBWs came from balls that did not turn — the straighter one. That is not a small thing. It is the off-spinner's weapon that makes a right-hander play for turn and then hits the pad on the straight line. Alongside it, he talks about working with elite coaches on angles and use of the crease. Crease variation and release-angle manipulation are precisely the marginal gains that separate a domestic spinner from a Test spinner. The spreadsheet said one thing; the stadium said another: the spreadsheet counts wickets, the stadium looks at the shape of the balls they came from.

There is another fact that should not be taken lightly: the Australia A match. It sits in the middle of a list of tournaments in the report, as if incidental. It is not incidental. It is the writer's strongest implicit argument — that Kotian has already bowled at near-international batting. That experience is not in the raw Ranji numbers everyone is quoting.

The age arithmetic that puts “timing” at stake

Kotian is 28 and his first-class career only took off in 2026 — the piece itself calls him a slow starter. Spinners traditionally mature late, and the writer says this in his opening line. The direct implication: at 28 he is at the door of his peak, not inside it. So the purple patch is plausibly sustainable rather than a one-season aberration — but the reverse is equally true. If this is the start of a peak, the selection window is now, not in three years. Ranji pauses until January 17 and the first Test is at Nagpur on January 21. The selectors will decide on the evidence already banked; Kotian cannot add another innings to his case. This is not a calendar convenience, it is a constraint.

And this is where the “timing” line stands on its own foot. The piece says the timing could not have been better, and the same piece's final paragraph says it will be “known over the next couple of months.” That collision of enthusiasm and restraint inside one report tells you the writer knows the selection is not settled.

Where my doubt lies, and how it could be falsified

Here I have to rein in my own habit. Thirty years of being right about the counter-intuitive call makes a man assume the most-quoted number is the most-wrong one. But discipline says: write down what would falsify your conclusion, alongside the conclusion.

My doubt is plain — almost all of Kotian's 37 wickets are on Indian surfaces, the very environment where Indian off-spinners are structurally most advantaged and where the data is least predictive of overseas Tests. Four Ranji innings is a small sample. Railways' lower-middle order and Australia's top six are not the same thing. And the biggest silence: the report has no data on performance against left-handers, against batters using their feet, or any phase-wise economy-strike-rate breakdown. So any assessment of his ceiling stays incomplete.

Now the test that would falsify my doubt. First — if Nagpur turns out to be a dry turner and Kotian gets a game, that debut will not answer his real question, it will push it further out. The real test is a long spell abroad, on a surface with no turn. Second — if selectors keep him only as a reserve and he plays no Test in the series, then “India need an off-spinner” was media noise, not team management's need. Third, and quickest — if he takes another 8-9 wickets in Ranji after January 17, the small-sample objection dies and the case is sealed. If he takes 2-3 in his next three innings, then the 37-wicket spreadsheet does what every transfer window does: it turns out to be the one number nobody trusted, and the one that was right.

What I will watch

I will not watch whether Kotian's name is in the squad. I will watch the category the announcement places him in — option, reserve, or future. Because the distance between a spinner's 37 domestic wickets and a selector's one sentence is exactly where Indian cricket's real selection machinery lives. The spreadsheet has said its piece. Now, if the selectors did not read that one fact written on the Brabourne surface, that will be their error, not Kotian's.