Mumbai Bowl Railways Out for 265 Chasing 372: Four Wickets in the Final Hour After Drinks

A jug of water, a paper cup, and then four wickets.

The drinks break came in the final hour on Thursday. Railways were 250 for six, Mumbai had set them 372, and what remained at the crease was a tail. What followed is the oldest and least-written part of cricket: four wickets, fifteen runs, and 265 all out on the board. The match ended there, having actually ended several hours earlier.

I was in Chattogram, in a hotel room, laptop open, sound off. For thirty years I have written cricket by hearing the bat — from the first tier at Wankhede, from the boundary rope at the CCI, from the outfields of Dhaka. This week I heard a laptop fan. This report begins with that gap, because the gap shapes every line in it, and hiding it would be a lie told to you.

So, first, the line that belongs at the top of every match report and almost never is: I was not at the ground. I had no pitch report. I saw no weather. I do not know what the light was like in that last hour, which way the wind blew, or how much the ball reversed. What I have is the scoreboard — an honest witness that counts and does not interpret. So the numbers here can be checked, the conclusions are derived from arithmetic, and the things I do not know will be labelled as things I do not know.

Context: Group D, 372, and an innings that belonged to two men

Ranji Trophy, Group D, Mumbai versus Railways. Mumbai set Railways 372. This is domestic first-class cricket, not Test cricket, and transferring its results directly to the international game is the mistake every season produces in somebody's column. Still, in four-day red-ball cricket, a target of 372 is a number that does its own work.

Railways' innings took this shape: 83 for five. Then 167 for the sixth wicket between Eshaan Goyal and Zubair Ali. Then Sarfaraz Khan's catch. Then, after drinks, 250 for six became 265 all out — four wickets, fifteen runs.

The whole innings collapses into a single line of arithmetic. Of Railways' 265, 167 came from one partnership; the other nine wickets produced 98 between them. That is not an opinion. It is addition, and it is the real story of this match.

The Mumbai names on the field are the familiar ones of the domestic circuit: the spin pair of Tanush Kotian and Shams Mulani, young batters like Musheer Khan, Suryansh Shedge and Divyaansh Saxena, and Sarfaraz Khan, whose name will be mentioned first after this match because he took a catch. Siddesh Lad's remarks referencing the Irani Cup and the CCI point to the same lineage — a Mumbai domestic structure that has run for generations on spin and batting depth. I did not independently verify that quote from a second source, and that belongs on the record.

What is not clear is whether the 372 was a declaration or the natural end of an innings. What is even less clear is the pitch. The source material records no venue, no pitch behaviour, no weather and no over-by-over detail. So saying 'the ball was turning' or 'the pitch had slowed' is speculation, not reporting. And when all you have is speculation, you should not print it as a conclusion.

Core: 83 for five to 250 for six, and then fifteen runs

Railways' central truth is that their top order made 83 and lost five wickets. Five wickets falling that early while chasing 372 is not an accident; it is pressure in its most ordinary form, the kind the scoreboard hides by writing '83/5'. The bigger the target, the faster a batter steps away from his normal game — and in domestic cricket that step away is the most expensive thing a batter does.

What followed was the best cricket of the match. Goyal and Zubair added 167 together. That stand matters because it proved the pitch was playable, the ball was not stuck in the surface, and the target could be broken into blocks. When a number six stays on the crease for four hours, he sends a message to the dressing room behind him: this can be survived.

But this is where the thing the highlights will never show is buried. The 167-run stand did not bring Railways back into the match; it only made the defeat arrive later. A target of 372 means roughly four sessions without a serious mistake. 250 for six means the men walking out next are the men who came to bowl. And bowlers, sent out to chase 372, do not produce miracles — they do their job and get out.

So the final hour's four wickets for fifteen runs was not a collapse. It was not a collapse; it was a queue. The sixth wicket fell, and the four names behind it had been sent out not to chase 372 but to eat time. There is no magic in the drinks break. The magic, if any, is in the fact that Sarfaraz Khan took a catch just before it — meaning the sixth-wicket stand broke at the exact point when the longest, most tiring stretch of the day was ending.

Sarfaraz's catch will be the most repeated image of this match. I am not undervaluing it — a catch at slip or short leg is always earned, and the work of the close fielder is the least written-about job in domestic cricket. But the picture and the cause are two different things. The catch happened because the ball was in the air. The ball was in the air because a batter who had been anchored for four hours was suddenly trying to do something else. The catch was the doorway; the lock had been fitted at the end of the partnership.

One more thing belongs on the record, because domestic coverage almost always drops it. Even at 250 for six, Railways had a route: one of Goyal or Zubair batting to the end with the tail clinging on. That route existed, but it required defensive batting in the final hour against two spinners, Kotian and Mulani, which does not fit the arithmetic of a 372 chase. A side chasing 372 cannot defend. That is the real weapon of 372.

Mumbai's win was therefore not built on one over, one catch or one spell. It was built on Mumbai making 372 first, and then letting the number do the rest. The first-innings batting — with young names like Musheer Khan, Suryansh Shedge and Divyaansh Saxena in it — will be the least discussed part of this match, and it was the difference. In domestic cricket, wins are usually written in the first innings and read out in the final hour.

A separate note on the spin pair. Kotian and Mulani are among the most reliable names on the circuit, and the load on both keeps rising. The Ranji calendar is four-day cricket, and a side with two spinners who can bowl on day four will bowl both of them thirty overs a match. This is the structure in which young and senior players alike are counted in overs rather than matches.

And on young players, one point that seems unrelated to this match but is not. Mumbai's system puts 19- to 21-year-old batters into the four-day red-ball rhythm because its depth means it does not have to wait. That depth is a strength on one side and, on the other, the reason a very small number of years absorbs a very large number of first-class overs. This scoreboard does not prove it. The season's scoreboard is slowly writing it.

The counter-read: the story that will be told is not the story of the match

In the next twenty-four hours you will read and hear three things. One, Sarfaraz Khan's catch was the turning point. Two, Mumbai's spinners turned the match in the final hour. Three, Railways' collapse was shocking.

All three have something in them, and all three are incomplete.

The catch was not the turn; it was the moment a partnership broke that could not have won the match anyway. At 250 for six, Railways needed 122 more, with four bowlers left at the crease. The catch did not change the result. It fixed the timing of the result.

As for the spinners: yes, they took the wickets in the final hour. But spinners taking wickets in the last hour of day four is not an extraordinary event — it is the most regular, most predictable sequence in domestic cricket. What was extraordinary was Railways getting from 83 for five to 250 for six. People will call that stand brave, and it was. But a stand that makes 167 while the team still loses by 107 runs decorates the scorecard without altering the outcome.

And the third — the 'shocking collapse'. A collapse is only shocking when hope remains. At 83 for five, hope was gone. Those calling this a collapse are in fact paying tribute to the sixth-wicket stand, and that tribute is deserved. But tribute and outcome are different things.

One old point here, in a single sentence, because it has not earned more. For forty years I have reported domestic cricket, and in every decade some reporter has written that 'the final hour turned the match'. Most of the time the truth was that the match had already turned, and the final hour was a formality. Forty years of keeping the beat, and the deadline still taps first — which is why the final-hour story always gets printed first, whether it is the biggest story of the match or the smallest.

And for those drawing Test-cricket conclusions from this: day four of the Ranji Trophy is not day four of a Test. Here a spinner bowls 30 overs, in a Test 45; here a batter chases 372, in a Test he thinks about batting out for a draw at 250. The shape of the result differs because the shape of the intent differs.

What to watch next

Group D's table arithmetic is now the most interesting thing in the competition, because Mumbai won this without their frontline pace attack, on spin and first-innings batting alone — and the question that follows into the next round is whether that load on Kotian and Mulani can hold for a full season. For Railways, the real question is not Sarfaraz's catch but their top order: 83 for five does not chase anything. And the thing I will watch in person next time is who carries the water at the drinks break. The scorecard is a number; the back of the team bus is the story — and the man carrying the drinks is often the man leading the side the season after next.