The Brabourne Spell That Turned Tanush Kotian's Test Claim Into Evidence

The ball was not gripping at Brabourne the way it had gripped against Haryana. That single sentence is the real clipboard behind Tanush Kotian's 7/45. Mumbai bowled Railways out for 259, took a 137-run first-innings lead, and stretched the overall advantage to 311 — the scorecard says this was a one-sided contest. But the scorecard does not say what kind of overs produced those seven wickets.

I have charted enough spin spells over the years to trust one rule: when the pitch offers no turn, a bowler's true craft shows up in the maiden count, not the wicket column. Kotian himself described Brabourne as a surface with less grip and said his focus was on accuracy, maidens and building pressure. This is exactly where the document and the measurement separate. The 8/81 against Haryana came on a turning track — a spell any spinner would dream of, but one the selection committee could comfortably wave away with "that pitch was built for him." The 7/45 against Railways is the answer that closes that easy excuse.

Five of the seven wickets were right-handers. That number looks small at first glance, but it cracks a large fault line in Indian spin selection. An off-spinner is often typecast as a matchup bowler against left-handers — the ball turning away, the LBW appeal, the obvious plan. Kotian showed in this match that he can be a threat against right-handers too, and that without significant turn. This is a straight technical-development question — use of the crease, changing bowling angles, mixing the straighter one with the stock ball. When there is no turn, the straighter one creates LBW and bowled chances — wickets built by architecture, not magic.

A balance is needed here. Kotian's season numbers read 37 wickets in seven first-class matches, 22 Ranji wickets in four games, and seven wickets in two matches against Australia A. That is a strong frame, but still a frame, not a building. A single innings of 7/45 does not by itself prove Test readiness; proof is built from three things — sustained wicket production, control on different surfaces, and performance against a full-strength batting order. Kotian has the first two. The third is yet to be established.

Mumbai's 311-run lead tells us Kotian did not have to bowl in a defensive situation — Railways were already under pressure. This is a detail the scorecard hides. When praising seven wickets, it is worth asking: did these come at 200 when Railways were strong, or at 150/6 when the tail was batting? The report gives no session-by-session detail, so my inference stays medium-confidence. But it is clear that if he bowled long, economical spells — building pressure with maidens — the performance is far more valuable to selectors than a short attacking burst. The context that changes things is overs and economy, not the magical wicket number. And that detail is missing from the report.

Now the angle that runs against the headlines. Framing this 7/45 as "the India door has opened" is easy, but Washington Sundar remains the stated first choice, and Saransh Jain is also in contention. Kotian's case at this moment is not for a starting spot but for a place in the squad or a reserve slot — and that may be his real strength. Sundar is the better batter, but Kotian also contributes lower-order runs (though the report gives no batting data, so calling him a "genuine all-rounder" would be premature). What sets him apart is that he took wickets against right-handers on a low-turn surface — potentially relevant against a team like Australia, where several batters are right-handed and pitches do not assist spinners early.

One more link is worth adding: seven wickets against Australia A. That number looks smaller than the 22 Ranji wickets, but its selection value is higher, because it is directly tied to the opposition environment that the five-match series will bring. Domestic cricket is a closed room until the India A door opens — and Kotian has walked through that door. That is the strongest link in his case, not the 7/45.

The risk is clear: Australian pitches will offer more bounce and less turn than Indian surfaces. Kotian handled a low-grip Brabourne track, but the bounce of Brisbane or Perth is a different problem. The report mentions no performance in overseas conditions, and that is the biggest question mark. The second risk is workload — seven first-class matches, India A games, and now a Rising Stars Asia Cup entry; with no over counts available, even estimating fatigue is impossible.

The real test for selectors is not whether Kotian is a good bowler. The real test is whether he fits the role India will need in Australia — second spinner, lower-order runs, and control in long spells. My next watch will be the official scorecards from the Rising Stars Asia Cup, and my forecast's expiry is explicit: if in the next three weeks his economy for India A stays below 3.2 and he scores 30+ in at least one batting innings, his name should be in the Australia series squad. If not, this 7/45 remains a good story, not evidence. The clipboard says one thing; the next three weeks will tell us what the 40 metres say.