Ranji Trophy Group D: Mumbai's 107-Run Win Was Decided in the Hour After Drinks
**मुख्य उत्तर:** मुंबई ने रणजी ट्रॉफी ग्रुप डी मुक़ाबले में रेलवे को 372 रन का लक्ष्य दिया और उसे 265 पर समेटकर 107 रन से हराया। निर्णायक मोड़ ड्रिंक्स ब्रेक के बाद का एक घंटा रहा, जिसमें रेलवे 250/6 से 265 पर ढेर हो गई। **मुख्य तथ्य:** - मुंबई ने 372 रन का लक्ष्य रखा; रेलवे की पूरी पारी 265 रन पर समाप्त हुई। - रेलवे 83/5 पर थी; एशान गोयल और ज़ुबैर अली ने छठे विकेट के लिए 167 रन जोड़े। - सरफ़राज़ खान के कैच के बाद रेलवे ने 250/6 से 265 तक 15 रन में चार विकेट गँवाए। - मुक़ाबला प्रथम श्रेणी (रणजी ट्रॉफी ग्रुप डी) था; इसके निष्कर्ष टेस्ट क्रिकेट पर सीधे लागू नहीं होते। - स्थल, पिच और कैलेंडर तारीख स्रोत में दर्ज नहीं; मैच सप्ताह के गुरुवार को खेला गया, आँकड़े सत्यापन के अधीन हैं। **स्रोत:** Stage-2 गहन विश्लेषण, क्रिकेट (एशिया घरेलू), रणजी ट्रॉफी ग्रुप डी मैच रिपोर्ट; प्रकाशन तिथि स्रोत में अपुष्ट — तारीख की पुष्टि से पहले आँकड़ों को अंतिम न मानें। **संबंधित प्रश्नोत्तर:** Q: मुंबई ने रेलवे को कितने रन से हराया? A: मुंबई ने 372 का लक्ष्य देते हुए रेलवे को 265 पर समेटा, यानी 107 रन के अंतर से जीत दर्ज की। Q: रेलवे की 167 रन की साझेदारी किन खिलाड़ियों ने बनाई? A: एशान गोयल और ज़ुबैर अली ने 83/5 की स्थिति से छठे विकेट के लिए 167 रन जोड़े। Q: क्या इस जीत से टेस्ट टीम के निचले क्रम के बारे में निष्कर्ष निकाला जा सकता है? A: नहीं; यह रणजी ट्रॉफी का प्रथम श्रेणी मुक़ाबला था और टेस्ट क्रिकेट की परिस्थितियाँ, समय और गेंदबाज़ी की गुणवत्ता भिन्न होती है।
The trolley came out, the glasses clinked, two batters took off their helmets, and the fielders scattered around the square began to drift back to their marks. On a Ranji Trophy ground, those are the ten minutes in which a match shows its real face — no camera behind the arm, no commentary box, just a few dozen people in one stand, a ball-boy by the boundary rope, and in the middle a partnership that had already decided the shape of the day. Eshaan Goyal and Zubair Ali had put on 167 for the sixth wicket. Railways had climbed from 83 for 5 to 250. A side that had been read as beaten by lunch now stood at a place from which chasing 372 looked absurd but not impossible.
The hour after drinks began, and the game turned. Sarfaraz Khan took a catch, and from 250 for 6 Railways were bowled out for 265. Fifteen runs. Four wickets. One hour. A stand that had lasted more than four hours ended in a moment witnessed by the few hundred people inside the ground and by nobody who will ever read the scorecard.
The scoreboard, as ever, tells everything and explains nothing. Mumbai set 372, bowled Railways out for 265, and won by 107 runs. Group D's table will record another win. The table will not record where the match was actually won — not at the point where the catch went up, but in the forty minutes before it, when Mumbai changed their intentions during that partnership and Railways did not change theirs.

This is first-class cricket, not Test cricket, and the distinction has to be fixed at the top rather than buried at the bottom. Ranji Trophy red-ball cricket runs on its own rules, its own calendar and its own economy. A declaration here is not decided by a broadcaster's prime-time slot but by tomorrow's humidity and a spinner's fingers. Matches finish inside four days because both sides need points, and the third session of the final day is where a captain's entire strategy narrows to a single question: do we have bowlers, or do we have time? Railways had time. Mumbai had bowlers. The bowlers won.
The whole match is built out of that one tension. Mumbai's 372 is not generosity; it is a statement of confidence. A side that sets 372 in the fourth innings is telling you that its spinners can take seven or eight wickets in a session on a last-day surface. Tanush Kotian and Shams Mulani are the collateral behind that confidence — one an off-spinner who keeps the ball fast and flat, the other a left-arm spinner who works relentlessly into the pads of left-handers. For several seasons that pairing has been Mumbai's most reliable asset in this competition, and the declaration rested on it entirely.
Railways' side of the ledger was the mirror image. Being 83 for 5 does not mean a team has given up, but it does mean the team has overs rather than runs. Goyal and Zubair began from the instinct that sits under every good rearguard: wear the ball old, knock the spinners off their lines, and hope the surface starts working for you by evening. Their 167 is both a story of resistance and the first half of a slow defeat, because when you build a stand that large for the sixth wicket, what waits behind you is number seven, eight, nine, ten and eleven.
Ranji Trophy lower orders are not a formality until a side is five down; at six down they become the structure itself. The partnership exhausted Mumbai's bowlers, but it also spent the overs that the rest of the order needed. When the sixth wicket fell at 250, Railways did not merely have five wickets left; they had five batters who would now face a hard ball, a packed in-field and a surface that had already taken the best part of their day's batting out of them.
The catch that started it needs to be watched separately from how it is understood. Sarfaraz Khan is among Mumbai's most experienced and most fearless names — a player who scored his way to the national team's door from domestic cricket, was sent back, and kept reclaiming the argument with his bat. In the Ranji Trophy his presence is a guarantee to any captain that a hand is standing at slip or short leg which will turn half a chance into a catch. But I am not here to say a catch turned the match. The truth is colder than that.
The catch only opened a door that Mumbai had already unlocked an hour earlier. The change in the bowlers' lines through the last phase of the stand, the field that was reset again and again, and above all the way the ball was worked away from the set batter to the non-striker — that was the preparation for the explosion that arrived after drinks. In Ranji cricket the drinks break is not an administrative pause; it is a weapon. The side that walks into it with a plan takes, in the fifteen minutes after it, what it could not find in three hours. Mumbai used those fifteen minutes. Railways absorbed them.
The second truth is that being bowled out for 265 was not a sudden accident but the working out of an old rule that domestic cricket regularly forgets: a tail-ender in the fourth innings is not prepared for a hard ball, and a spinner does not beat him by tossing it up but by keeping it flat and straight and letting him make the mistake. Four wickets for fifteen runs is not a collapse of spectacular deliveries; it is four different batters arriving, one after another, at a ball they had not faced all day.
This is where an old habit of mine surfaces, one I carried from county grounds in England to domestic grounds in India: I read the scorecard before I read the report, and the first thing I look for is the over in which the partnership broke. The ten overs after a stand ends are the most honest document a match produces. The journey from 250 for 6 to 265 all out — four wickets inside fifteen runs — is a document no highlights package will ever show. I went looking for the score and found the silence first; silence is a statistic too, just one nobody puts in a column.
What will sting Railways most is that two of their batters did the hardest job this competition asks for — carrying sessions with five wickets already gone. Eeshan Goyal and Zubair Ali added 167, a number that reads like a weather report: it tells you the team has technique, patience and, most importantly, an understanding that time is not the enemy in red-ball cricket. It also tells you how heavily the rest of the order leaned on them. When a team's sixth-wicket stand is the largest single component of its match, expecting the number seven to survive a hard ball, the humidity and the spin for a session and a half is the most common and most expensive error in the game.
The credit for this win belongs to Mumbai's spinners and to the captain's patience during the stand, not to a single moment in the final hour. That patience is invisible from the boundary. It shows in the decisions — swapping ends mid-partnership, keeping an attacking field, and still holding something back for the last session. In domestic cricket that is what separates captains: not who sets the better field, but who knows which part of the day his bowling resources are actually for.
On Mumbai's batting, the number is plain: 372. Setting that target is never only about runs. It encodes a belief that the opposition's batting depth will not reach it, and that belief sits on a surface that changes with the clock. Musheer Khan, Suryansh Shedge and Divyaansh Saxena belong to the generation Mumbai has been pushing forward across recent seasons — young batters who make runs in domestic cricket and whose road ahead runs through the long national selection queue where the weight of regional numbers shifts every year. That is Mumbai's strength and its dependence at once.
Now to the part where I have to be careful, because this is where the story takes its easiest turn.
The easy version goes like this: Mumbai set 372, Railways fought back through a record stand, and then a Sarfaraz catch turned the game. It is tidy, it fits a paragraph, and it leaves the reader with nothing to ask. That is my problem with it. Tidy stories are usually press releases rather than match reports.
The real story is that Railways lost this match at 83 for 5, not at 250. Losing five early wickets meant the sixth-wicket stand had to do two jobs at once: score runs and eat overs. A partnership doing two jobs slows itself down, and a slow partnership leaves nothing behind for the batters who follow. In other words, the stand that saved the team was also the stand that exhausted it. The moment it broke, the four remaining batters had no freshness, no overs and no partner at the other end to hold the line.

None of this transfers directly to Test cricket, and here I want to stop myself. In Tests the tail often arrives with better technique and a longer defence, DRS exists, the new ball is used differently, and above all the quantity of available time is different. A final-day session in the Ranji Trophy can look like a fifth-day session in a Test and behave nothing like one. Teams here play for points, declarations carry a different pressure, and the average quality of the bowling is different. Anyone drawing from this match a conclusion about India's Test lower order is putting two different worlds on the same scale. I will not do it.
The other thing that gets lost is the quiet of the ground. A Ranji Trophy match is cricket in its rawest condition — a few hundred spectators, a half-filled stand, some families, a few men with old scorebooks, and a tea stall outside the gate. When Sarfaraz took that catch, the noise was as large as the ground allowed it to be. That does not make the moment small; it means the moment had very few witnesses. I went looking for the score and found the silence first, and that silence is what brings me back every domestic season, because where there is no camera, cricket is played on its own terms.

One quote from this match stayed with me. Siddesh Lad measured the win against Irani Cup memories at the CCI. It is a short sentence carrying an entire memory system. The Irani Cup is the old hinge of the Indian domestic calendar, played between the Ranji champions and the Rest of India, and the CCI ground is its oldest witness. When a senior player reads a Group D win through that lens, he is saying that the season's meaning for him is not only points — he is looking at the staircase that leads to the stage where someone will remember him.
Memory has a surface and a bounce, and in domestic cricket that surface is built out of grounds like the CCI. A player who has once played there measures every later match against it. That is why a Ranji win should not be read only through the points table. The 107-run margin is for the table; the real difference is that Mumbai's spinners proved again they can dictate the clock of a match on a last-day surface, and Railways showed that the spine of their batting still ends at number six.
For me this match will be remembered for one more reason. I have spent more than twenty years around domestic grounds, and the scene never changes — the drinks trolley, the helmets coming off, and the fifteen minutes in which the match turns. It is like a weather report: you look outside and make a guess, but the temperature is the one you learn about afterwards. Every Ranji match is a weather report from a place you have not yet lived in — you know Eshaan Goyal's name because he was part of a 167-run stand, but you do not know which team he will play for next season, or whether he becomes the spine of Railways' batting or does not.
The cold truth of this match is that all four numbers — 372, 167, fifteen runs for four wickets, and a 107-run margin — say the same thing. Railways played very good cricket twice in this game, and both times it did the work that does not win matches. The first was the climb from 83 for 5 to 250. The second never came, because after drinks Mumbai did not allow it to.
What next? For Mumbai this is not a declaration win in the romantic sense. It is the kind of win domestic cricket calls bowling depth. A side with two spinners of different temperaments in Kotian and Mulani can set 372 in the fourth innings as arithmetic rather than risk. The question is whether the arithmetic holds on a day the surface offers nothing, or against a side with three solid batters after number six. The rest of the Ranji season is the wait for that question.
For Railways the question is blunt, and the answer is not in the batting order but in selection thinking. A team whose hopes rest on a sixth-wicket stand cannot defend for a day in a four-day game. If numbers eight and nine have to face a hard ball, the story ends there, as it ended here after 250 for 6. In the matches ahead, this side has to find batters at five and six who turn partnerships into runs rather than into a fight for survival.
As for Sarfaraz Khan, that catch is the signature of a player who stays alert in the deadest hour of a match. In domestic cricket that alertness is a currency. But when people remember this game, I would like them to remember as well that the 167 runs before the catch were made on the same ground where no camera was watching. The column refused to start with the score, so it began with a drinks trolley — because the hour that followed that trolley decided how large 372 would be, and how small 265.
The question is not whether Sarfaraz took the catch. The question is what a team's plan will be for the fifteen minutes after drinks, the next time it puts on 167 for the sixth wicket — because that is where Ranji Trophy matches are decided, in the hour where no camera is present.
