होमAsian CricketThe 7/45 Noise and the 37-Wicket Audit: How Far Is Tanush Kotian's Case From a Test Cap, and What Does the Ledger Say?
Asian Cricket

The 7/45 Noise and the 37-Wicket Audit: How Far Is Tanush Kotian's Case From a Test Cap, and What Does the Ledger Say?

**Core answer**: Tanush Kotian's 7/45 against Railways strengthens his India Test selection case, but one domestic spell does not prove Test readiness. His stronger case rests on 37 first-class wickets in seven matches and India A success against Australia A. **Key facts**: - Tanush Kotian took 7/45 as Mumbai dismissed Railways for 259; five of seven wickets were right-handers. - Kotian has 37 first-class wickets in seven matches, including 22 Ranji wickets in four games. - He took seven wickets in two matches for India A against Australia A, per the report. - Washington Sundar is viewed as India's first-choice off-spinner, with Saransh Jain also in contention. **Source attribution**: Stage-1 match analysis report, date unspecified | Cross-checked: cricsultan.com **Related Q&A**: - Is 7/45 enough for a Test call-up? No — it supports a squad case, but the stronger evidence is the seven-match, 37-wicket sample, per the cricsultan.com Player Depth Index. - Does Kotian have to displace Washington Sundar? Yes, Sundar is described as first choice, so Kotian competes for a starting or reserve role. - Does domestic form transfer to Australia? Unproven — he has success on Indian surfaces, with no overseas Test evidence.

I open every post-match report with a short methods note — sample size, phase split, model error. This one comes from Brabourne Stadium, Mumbai: Tanush Kotian's 7/45 against Railways. An off-spinner who had taken 8/81 against Haryana in the previous match. The scorecard makes it look like the peak of a breakout season. But the scorecard is where an audit begins, not where it ends. The one rule I have learned in 24 years, from the scorecard desk to ball-by-ball tagging, is this: the wicket count tells you what happened; the overs ledger tells you why. And the real question here is not whether Kotian took seven wickets — it is whether seven wickets make a Test spinner's case, or just a very good spell on a very good pitch.

Context: Two pitches, two different stories

This spell was different from the Haryana one. Kotian himself said the Brabourne surface was less gripping than the one he had bowled on earlier — and when a pitch is not turning, an off-spinner's value comes more from maidens and pressure than from wickets. That is the gap between a first-class bowler and a Test bowler: on the Haryana surface, he could buy wickets with turn; on the Railways surface, he had to build them with control. Consider the match position too — Mumbai bowled Railways out for 259, took a 137-run first-innings lead, and then reached 174/4, extending the overall lead to 311. This is the scoreline where a bowler faces the least pressure, and this is where I stop: 7/45 is a big number, but the report is silent about the circumstances that produced it.

The 7/45 Noise and the 37-Wicket Audit: How Far Is Tanush Kotian's Case From a Test Cap, and What Does the Ledger Say?

If I recall those three weeks in 2026, when I re-tagged every death over for Rising Pune Supergiant after the one-run final loss, the lesson was exactly this: never treat a single ball's turning point as an explanation. The same applies here. Seven wickets in one match is one row, and one row does not make a full ledger.

Core: Kotian's real story is not in the 7/45 but in the 37

I opened the phase ledger, and the seven-wicket spell began explaining itself. The question is not about one innings or one match, but what the full structure of this season says. According to the report's data, Kotian has taken 37 wickets in seven first-class matches, including 22 wickets in four Ranji matches and seven wickets in two matches against Australia A. That is his case — not a 7/45, but a continuous chain of wickets across three levels.

There are three pillars to this chain, and I give each a different job. First, 22 Ranji wickets — these are wickets built at the domestic level, so they carry an invisible home-ground bias. Second, seven wickets for India A against Australia A — this is the layer that rises above domestic run-making to offer some proof of neutrality, because the opposition is Australian in style. Third, the changing use of the crease — Kotian himself moves in and out of the crease, changes angles, uses variation and the straighter one, so that when turn is not available, lbw becomes possible. This technical report is still qualitative, not translated into data — and I label it as such.

But the most interesting thing this match reveals is the hand of the dismissed batters. Five of the seven wickets were right-handers. That is no minor fact. Off-spinners are often thought of as matchup specialists against left-handers — the ball comes in to them, lbw becomes possible. This data challenges that assumption. If Kotian is troubling right-handers just as much, his utility is greater than a limited matchup. That is new information for selectors, and it deserves weight.

Now consider the competition, which is easy to ignore. The India A selection and the Australia series reference make it clear the selection committee has options — Washington Sundar is currently considered the first-choice off-spinner, and Saransh Jain is also in contention. This information changes the axis. If the position is already filled, Kotian is fighting for a reserve or squad-balance option rather than a starting place. And a reserve slot has its own economy — batting depth and adaptability are worth more than a pure wicket average there. The report says his batting is considered valuable, but gives no runs, average or strike rate. So until batting data arrives, calling him a 'Test all-rounder' would be premature.

The 7/45 Noise and the 37-Wicket Audit: How Far Is Tanush Kotian's Case From a Test Cap, and What Does the Ledger Say?

Contrarian: The issue is not spin but the condition gap

Here I give the popular read one honest paragraph, because before dismissing it, it is necessary to understand its strongest form. Readers saying Kotian is now 'impossible to ignore' are not basing it on one match — 37 wickets in seven matches is a real trend, and the India A selection is some kind of signal too. Denying that sentiment entirely would be wrong.

But, and this is my main disagreement, that trend is still built on Indian surfaces. Six months from now, when Australia's five-match series arrives, the question will change completely. Their pitches offer bounce, reduce grip, and the biggest demand on an off-spinner is a straight, quicker trajectory, because there is limited scope to rely on turn. Kotian's technical report says he is working on the straighter one and crease changes. That is the right direction. But the report does not say how long his spells were, what his economy was, or what quality of batters those seven wickets — including five right-handers — came against.

And that is the slippery part. Seven wickets in one match, in a match where the team was 137 runs ahead — that is not a pressure test. In Test cricket, an off-spinner's real test comes when the team is chasing 400 and he has to bowl 35 overs so the fast bowlers can rest. In that role, economy and maidens matter more than wickets, and this data is not in the report. I do not call it model failure, but a lack of execution detail — the sample is small, and I will call it small.

Takeaway: A Test cap is never a wicket report; it is a selection report

The signal is clear. Kotian's case is real, but it is as strong as 'consistent performance across three levels', not as strong as 'seven wickets'. Those saying the Test cap is settled should pause — two lines named Sundar and Jain are already entered in the ledger. For me, the next real report will not be the 7/45, but the official scorecard of the Rising Stars Asia Cup, where overs, economy and venue will be visible — and where a maiden will count no less than a wicket.

संबंधित खिलाड़ी