The Dry Day at Brabourne and Kotian's Moisture: The 7/45 Story the Scorecard Doesn't Tell

On that Wednesday at Brabourne Stadium, a veteran food vendor was folding up his cart outside the ground while Tanush Kotian was searching for the second-finger release on the ball—the very ball that had scattered 8/81 against Haryana a few days earlier. Railways had folded for 259, Mumbai had taken a 137-run first-innings lead, and by the fall of the fourth wicket the hosts had reached 174/4, extending the overall lead to 311. The ink on the scorecard was drying, but the Brabourne pitch lacked the moisture that forces a spinner to bend it to his will. Kotian said as much after the match: "The pitch wasn't gripping." That one sentence changes the value of those seven wickets, because the hardest bowling isn't where the pitch wins you the game; it's where you have to win without the pitch.

First-class cricket in India has its own strange economy. Anyone who has read Ranji Trophy scorecards knows that seven wickets become easier when the pitch starts to wither before the fourth day and the bowler simply waits by landing it in the right spot. But a surface like Brabourne's, which neither bakes into dry dust like Haryana's ground at Rohtak nor takes traditional turn like Chepauk in Chennai, makes the bowler's task more mental than technical. The essential fact of Kotian's 7/45 is that he could force batters to bend to him even without help from the pitch. Dismissing five right-handers from Railways—when he has been known primarily for his accuracy against left-handers—is a signal that cannot be seen purely in the light of statistics. This is the story of a cricketer stepping beyond the boundaries of his own identity.

In the Ranji Trophy matches I have watched over the past few years—and my experience says domestic coverage is no longer what it was, with only knockouts and a few big games making it to television—a clear pattern emerges. When an off-spinner takes seven wickets on a dry pitch, the talk is of his "rip." But when the same bowler takes seven on a low-grip pitch, the talk should be of his "understanding." What Kotian did in this match is a sample of technical evolution that I have seen several times in my 45-year career, though it surfaces differently each time. Use of the crease, changing angles, a straighter one that goes away from the stock ball, and above all building pressure through maiden overs—these are the marks of a bowler who doesn't just take wickets but breaks a batter's patience.

But there is a truth here that I know from experience and that no scorecard reveals. There is an old saying in cricket—I have heard it in Urdu—"har chamakti cheez sona nahi hoti" (not everything that glitters is gold). Hidden in the shine of Kotian's seven wickets is the morale with which Railways' batting lineup walked out. To be bowled out for 259 in the first innings and then face a mammoth deficit of 311—that is a situation where batters have already conceded, and the bowler gets less credit for it. I am not saying Kotian's performance was weak; I am saying that in domestic cricket, the figure of "seven wickets" can be as misleading as "five wickets" in a Test match. The real question is: did Kotian take those wickets under pressure, or when the match was already in Mumbai's pocket? The report has no session-by-session detail, no length of bowling spells, and no mention of the condition of the ball. This is the gap where I stop my pen.

One more thing to remember when evaluating this performance. Kotian has taken 37 wickets in seven first-class matches this season, including seven wickets in two matches against Australia A—that is the most relevant part. India face a five-Test series against Australia, and selectors are influenced not just by Ranji Trophy numbers but by the experience a bowler has gained against Australian batters. Kotian's seven wickets against Australia A is a bridge, but that bridge is only half-built, because the conditions of those matches, the quality of the batters, and the bowling workload are all unknown. Still, it is a signal that cannot be ignored.

Now the point I find most important in this whole matter—and this is part of my own intellectual journey. I belong to the generation that believed in a very simple rule about selecting spinners in Test cricket: if he is taking wickets in domestic cricket, give him a chance. But the data desk has taught me that this rule is insufficient. Today selectors have tools like matchup profiles, phase profiles, and expected runs, which tell them how effective a bowler will be in a given situation. And that is where names like Washington Sundar and Saransh Jain come in. It is no secret that Sundar is currently the first-choice off-spinner, and Saransh Jain is also a contender. Kotian's case is not weak because his numbers are poor; it is complex because the chair he wants to occupy is already taken.

Here is a fact I would like to connect with my experience. After the 2026 Champions Trophy final, when Pakistan beat India by 180 runs, I watched that match not from the commentary box but from the stands. That day I felt that the real story of a match lies not in the scorecard but in the emptiness that descends on the ground after the last wicket falls. I see Kotian's 7/45 through the same lens. It is a performance that pushed Mumbai into a strong position, but it does not yet prove that he can win matches for India on Australia's flat pitches. The real test is still ahead—and that test will not be in Ranji Trophy scorecards but in future India A tours and a potential Test debut.

For me, the most interesting question is how Kotian himself handles this pressure. After the match he said the selectors would decide—a mature statement, but it also shows he knows this battle is not just about wickets. In Indian cricket, the off-spinner's slot has always been a political chair, and here "fit" matters more than "form." Is Kotian a better option than Sundar in terms of team balance? His batting has been described as "valuable," but without numbers that claim is incomplete. Will his experience work against a team like Australia? Seven wickets against Australia A is a good sign, but this is not the same Australia that wins the Ashes.

I admit my perspective comes from the old school where domestic performance was directly equated with Test capability. But I have another experience too—the period of 2026-21 when I stopped watching cricket for six weeks because, during the pandemic, canned crowd noise was being piped into my headphones in empty stadiums. That phase taught me that the real value of sport lies not in its statistics but in its circumstances. Kotian's 7/45 is that kind of number—it cannot be seen in isolation from its circumstances. The Brabourne pitch, Railways' weak morale, Mumbai's strong lead—all of these are hidden within that 7/45.

Now a dimension I often return to in my writing: the gap between the commentary box and the data desk. I have seen in my career that the data desk settled tactical debates years ago, but the television commentary box still runs on the old template. The discussion about Kotian's performance will also fall victim to this gap—some will see only the magic of "seven wickets," while the real question is under what circumstances and under what pressure he took them. If I were in Kotian's place, I would try in my next bowling spell to prove that I am not just a bowler of dry pitches—and perhaps that is why he said after this match that the pitch wasn't gripping. He knows his real evaluation begins now.

One more thing that bothers me in this story is the transparency of the selection process. Will selectors weigh Kotian's case against Sundar and Jain purely on wicket count, or will they also look at bowling control, batting value, and team balance? The report gives no indication. I have seen many selection controversies in my 45-year career, but I think this time the matter is different—because Kotian's name has emerged not just from Ranji Trophy numbers but from India A experience. That is a change I consider positive.

Finally, I want to say something that is perhaps the most important comment in this article. Tanush Kotian's 7/45 has brought him to a point from where the door to a Test cap is visible, but that door is not yet open. Indian cricket's history is full of bowlers who took hundreds of wickets in domestic cricket but never got the Test place they hoped for. What Kotian has is time—he is still 26-27 and has at least four-five years to learn. But how that time is used depends on what he learns from his Australia A experience and how selectors assess his potential.

As for me, I want to end this article the way I began—with a small thing. On that ground at Brabourne, when Kotian must have bowled his last over, perhaps only a handful of spectators remained in the stadium. None of them would have thought that this seven-wicket performance would become part of a debate over selection for a Test series. But cricket works like that—an afternoon's labour on a small ground, and then it becomes part of a larger story. For Tanush Kotian, this story has just begun. And for me, it is another opportunity to write that story in its proper context—not just in praise of seven wickets, but in appreciation of all the labour that hides behind such numbers.

If I had to say it in one sentence: Tanush Kotian has proved through his 7/45 that he is not just a "turning-pitch bowler," but to prove he is a Test bowler he still needs one more performance on one more kind of pitch—and that pitch will be in Australia, where patience, not turn, matters.