From 250/6 to 265: Railways' 372 Chase, a 167-Run Stand, and the Hour After Drinks

On Thursday afternoon, immediately after the drinks break, the Railways scoreboard read 250/6. Chasing 372, four wickets in hand, two set batters at the crease — Eshaan Goyal and Zubair Ali, who had lifted the side from 83/5 to 250 with a sixth-wicket stand of 167. In first-class cricket that is precisely the hour in which a match is either saved or scattered in half an hour. Railways scattered. Four wickets inside 15 runs, all out for 265, and Mumbai won the Group D fixture by 107 runs.

I read the card three times. All three times one figure sat highest — 15/4. Not 219, not 372, not 167. Just 15/4. Anyone reading cricket as narrative will begin with Sarfaraz Khan's catch. Anyone reading it as a ledger stops on that one line.

Context: the match was made before Thursday

Mumbai set a target of 372, and that is not a coincidence, it is a calculation. In domestic red-ball cricket the size of a target is not set by the runs alone; it is set by how much the pitch will break on the fourth innings and how much time the opposition has left. 372 is the number at which the batting side stops playing to win and starts playing not to lose. Railways did the second thing for two days.

According to the available scorecard, Mumbai's line-up carries Musheer Khan, Suryansh Shedge, Divyaansh Saxena and Siddesh Lad, with Tanush Kotian and Shams Mulani as the spin pair — bowlers known domestically for long spells, not four-over bursts. In a first-class game a spinner's job is less about taking wickets and more about buying overs; on a fourth-day surface that equation reverses.

The Cricket Club of India appears only once in this material — in Siddesh Lad's remark referencing the Irani Cup. That tells us nothing about this pitch. Pretending otherwise is the easiest sin in this job. Weather, dew, light, how the surface behaved: none of it is recorded. So the analysis below rests only on what the card supplies, and where there is inference, it is labelled as inference.

Core: the 167-run stand, and what Mumbai changed

Eighty-three for five to 250 for six is not routine in domestic cricket, especially with 372 on the board and the closing session of a day available. Eshaan Goyal and Zubair Ali did something technically clear: they did not block the ball, they scored — but they scored into the gaps where Mumbai had no fielder. In a chase, the greatest risk in first-class batting is not a good bowler; it is being forced into singles and surrendering the space to hit. A stand of 167 means both batters kept the right to score on their own terms.

That stand did not simply break. It was broken. And the sequence the card shows is unambiguous: after drinks, Railways lost their last four wickets inside 15 runs. No side loses wickets because of a drinks break. The break only makes visible what was already running — tired legs, a set batter losing his rhythm, a new man at the other end, and above all a small bowling change that had till then been deferred.

One of those four wickets is credited to Sarfaraz Khan's catch, and the card records it as a catalyst — the queue of wickets begins right after it. A catch does not win a match. What wins it is the field setting that made the catch necessary in the first place. Set batters with four men on the boundary take singles and the catch never arrives. The moment Railways reached 250, Mumbai had nothing left to protect — 122 needed with four wickets in hand had already collapsed to something like 60 or 70. That is when Mumbai attacked, because by then they had nothing to lose. The oldest lesson of first-class cricket, and the least written: defensive fields take wickets and attacking fields take wickets; the difference is who can afford patience.

Mumbai's bowling resources suggest the clatter was not going to last long anyway — Kotian and Mulani are most useful in exactly this passage of play, because domestic bowlers get fourth-innings help from the surface and have the habit of patience to go with it. The sixth-wicket pair suddenly had to bat in a different rhythm: the ball was turning, the field was close, the shot-making arc was small. Those three things together produce 15/4.

Also read: Thirty-One Nights of Somebody Else

One thing is buried deepest in this match and matters most: the two men who added 167 are not the names at the top of an IPL auction list. Eshaan Goyal and Zubair Ali batted four hours each, wore down two Mumbai spinners, and manufactured a game Railways could not have lost had one more wicket been in hand. The philosophy of that stand is simple: making runs in the Ranji Trophy is one thing; making runs and dragging your team back into the match is another. No auction buys the second thing.

Contrarian angle: not the catch, the declaration

The easiest story is that Sarfaraz Khan's catch turned Railways' innings. That may be true, but the truth points the wrong way. Winning by 107 runs is not evidence that the last hour matters; it is evidence that in the first three days Mumbai built a board of 372 and left Railways no road except batting. Teams brave about declaration in domestic cricket do not believe wins come from targets; they believe wins come from time. 372 is the number that keeps all four results open — win, loss, draw, and possibly a one-innings finish. Railways batted to win, and that is why they lost. Had Mumbai declared at 300, Railways might never have been 83/5 — and the match might have drawn.

The second uncomfortable thing: every number here comes from the available scorecard and is pending verification. The match is described as Thursday's; no date is recorded. Individual scores, bowling figures, the exact time of the drinks break — none of it is confirmed. For a reporter this is honesty, not weakness. What the card does not say must not become commentary. Equally, what the card does say must not be ignored: 15/4 holds as much truth as the 167 stand, perhaps more, because a partnership can be dismissed as two men's effort while four wickets cannot — they are the output of something that had been working quietly all day inside a team's structure.

I chose to write the pause after the roar, where the athlete becomes a person again — and in this match that pause was the drinks break. Nobody did anything there. One team got up, the other did not, and the difference between them became 15 runs in the final hour.

What to watch next

For Mumbai, these four points in Group D are the kind that keep in the latter half of a season — there is no substitute for a home win in red-ball cricket. For Railways the question inverts: coming back from 250/6 to 265 once is a wobble, twice is a pattern, a third time is ugly. The season is long and every draw pushes a team up the table if it does not lose — but no draw puts it at the top. The scoreboard is telling Railways it may have the bowling and the stomach for a long innings; the only question is which over the stomach breaks in. The day that break arrives before the drinks interval, sides like Mumbai will have to do a different calculation than 372.