Ranji Round 4, Day 4: The Scorebook Behind Mumbai's 311-Run Lead, and Three Matches That Could Flip in an Over

Mumbai's account shows a 311-run lead. Against Railways, on Day 4 of Round 4 of the Ranji Trophy. The figure looks as clean as it is incomplete. I have kept the same page open for twenty-five years, so I know that when a scorebook leaves a number this vague — no innings state, no time remaining, no pitch report — it is usually somebody's convenience, not an accident.

Mumbai are in a strong position. That is not a lie. But between "strong position" and "outright win" lies the gap where four days of Ranji Trophy quietly become a draw. You have 311 runs, but how many overs remain? What state is Railways' second innings in? Is there a batter at the crease who can hold two sessions on a third-day pitch? None of those answers are in this update. And the questions nobody asks are the ones that matter most.

Context: Day 4, four different stories

Round 4 of the Ranji Trophy is on its fourth and final day. Across several grounds, matches are moving toward decisive finishes — the hour when the real tension of domestic cricket surfaces. No commentator, no DRS, no prime-time slot. Just the scorecard, a captain's eyes at the tea break, and a bowler who knows the next two hours will write his career's address.

Four main stories define the day. Mumbai's 311-run lead; Saurashtra folding to 134/8 while chasing 342; Himachal Pradesh struggling at 83/4 in pursuit of 447; and Meghalaya's chase of 295, which began with Raj Biswa dismissed for a duck. Tamil Nadu are closing in on a bonus-point win over Chhattisgarh; Uttarakhand have already beaten Haryana by ten wickets.

But if you try to weigh these four scorelines on the same scale, you will get it wrong. These are four separate matches, four separate pitches, four separate teams and — most importantly — four separate standards of score update. In some, the target is clear; in some, the wickets are counted; and in Mumbai's case, only a difference has been left behind under the label "lead."

That is where my problem begins.

Core: only what can be counted is true

Tanush Kotian's seven-wicket haul. This is the cleanest, most solid number of the day. Seven wickets in an innings is a statement in domestic cricket, especially when you are playing for Mumbai and the job is to bundle a side like Railways cheaply in the first innings. But let me tell you what is not in that number: how many overs, how many runs, on what pitch, in what breeze, and most importantly — whether those seven wickets came from one mode of bowling or three different tricks. A seven-wicket haul is the data of one innings, not a career. I learned that on my own sheet of 340 ODIs — a one-off miracle and a repeatable pattern look identical until you see the third instance.

Angkrish Raghuvanshi and Divyaansh Saxena's half-centuries. Two young batters, two fifties. Good news, but incomplete. Off how many balls? In what situation? Did those fifties take the team from 250 to 350, or from 400 to 450? In the Ranji Trophy, the value of a half-century is set by its context, not its number. In 2026, at the M. Chinnaswamy, I watched a final in which 23 deliveries went missing from the official scorebook across four days — wides, no-balls, and a leg-bye that never reached the card. Since that day I have never judged an innings by its total. Fifty runs means only what is written around it.

Saurashtra's 134/8, chasing 342. Here the arithmetic is very clear, and that is exactly why this is the most reliable update. 208 runs needed, two wickets left. Cricket offers no crueller position — hope is neither dead nor alive. Tripura are two wickets from sealing the match. You could say it is nearly settled. I would say it belongs to the category of nearly-settled in which I have seen at least a dozen reversals in thirty years. If the last pair holds out for 45 minutes and rain arrives, a mountain of 208 can shrink inside 30 overs. But on the available information, Tripura's position is the strongest. That is a fact, not a forecast.

Himachal Pradesh's 83/4, chasing 447. This is the kind of position a scorebook dismisses as "difficult," and that is the word that irritates me most. 364 runs needed, six wickets in hand. In the fourth innings. On a fifth-day pitch. If you ask me the probability of winning this match, I would say the question itself is wrong. The right question is: does Himachal have six wickets capable of batting four sessions? The answer is not in the scoreline, and therefore any decisive comment on this match is merely rumour.

Raj Biswa's duck. Meghalaya are chasing 295 and have lost a wicket at the start. It is a blow, but a duck in one innings is not proof of a technical weakness. I have seen batters dismissed for nought one day and hit a double hundred the next match, and I have seen ducks that were the start of a long bad run. The difference is only this — the first had a next match, the second had an excuse.

Now the part most often ignored. Tamil Nadu are closing in on a bonus-point win, but the bonus-point rules are not supplied in this report. This is where domestic cricket coverage commits its biggest omission. We report the win but not the arithmetic of it. Where a bonus point places a team in the group table requires knowing the rules — and the rules usually stay outside the scorecard. My sheet always has a separate column: "what does this win change in points?" If there is no answer, the story is half-told.

Contrarian: the biggest enemy of a 311-run lead is time, not the opposition

Here I arrive at a conclusion that looks inverted at first glance. Mumbai's 311-run lead is not the greatest guarantee of their victory — it is the greatest uncertainty about it.

The reason is simple. A 311-run lead means Mumbai have spent a lot of time on the ground. Day 4 is half gone. If Railways' second innings has only just begun, Mumbai may have perhaps 60-70 overs left for an outright win. In those overs they must bowl Railways out twice — or bowl them out once and not bat again. But if Railways' second innings is already underway and they have kept three or four wickets in hand, Mumbai may have to settle for the satisfaction of a 311-run lead.

This is the trap every major domestic side falls into sooner or later. Mistaking a lead for a win. In 2026, on my sheet of 340 ODIs, I saw a different kind of pattern — the frequency of no-balls in the first three overs, the collapse of run rate immediately after a set batter's dismissal. In those eleven matches that sat three standard deviations out, the result was never written in the scorebook — it was written in the sequence. The same applies to Mumbai. 311 runs is a state, not a sequence. The sequence is: how many overs remain, who will bowl, is the pitch breaking, and does Railways have a batter who can hold two sessions in a fourth innings. Not one of those answers is in this update.

And here a second thing grates. Tripura's position is decisive over Saurashtra, but it too is a snapshot. 208 runs needed, two wickets left — the arithmetic is so clean anyone would treat it as the final result. But in the Ranji Trophy, the last pair sometimes writes the story nobody wants to read. If that pair holds out two hours and rain eats a session, a target of 208 can become a draw. I am not saying it will happen. I am saying that until you have the final scorecard, you have nothing.

One more point on Biswa's duck. Losing an early wicket while chasing 295 is bad news for Meghalaya, but from that single innings you can say nothing about Biswa's form. In 2026 I read enough scorecards in one season to understand this — the data of one innings is a sentence, the data of a season is a paragraph, and the data of a career is a book. Those who write a book from a duck usually read the first page and claim the last chapter.

Takeaway: tomorrow morning's scorecard, not this afternoon's news

When you open the scorecard tomorrow morning, look at three things.

First — how many overs Mumbai had left and what state Railways' second innings was in. If Railways saved the game with four or five wickets in hand, the 311-run lead will remain a number nobody remembers. If Mumbai took an outright win, Kotian's seven wickets will be called the foundation — but the truth will be that the win was caused by time management, not by wickets.

Second — how long Saurashtra's last pair lasted. Getting from 134/8 to 342 is nearly impossible, but getting from 134/8 to a draw is very possible. If that pair batted 40 overs and the match was drawn, it will be a defeat for Tripura that does not look like a defeat in the scorebook — but in the points table it will look exactly like one.

Third — how long Himachal's six wickets lasted. Chasing 447 while 83/4 is a position any report dismisses as "almost a loss." But the word "almost" is used only by those who do not read the scorecard. If Himachal's lower order survives two sessions, it will be a draw nobody calls a win — yet in the book of cricket it will be worth as much as any thrilling victory.

I have kept one page open for twenty-five years. And even today, when I see a scoreline, the first thing I ask is: where is the rest? What is visible is half the truth. What is not visible will decide everything.

Day 4 of the Ranji Trophy is drawing to a close. Tomorrow morning, when the scorecard is complete, we will learn who won today and who merely survived.