Ranji Trophy: Maharashtra's 75-Run Lead Is Really About the Clock, Bengal 76/4 and Behind

Walking out of the Eden Gardens pavilion, I saw the evening light slanting across the ground like steam rising from a tea-stall kettle. On the final afternoon of Day Three, the umpires looked at the light meter and shook their heads; the faces of both coaching staffs told you this was no longer just a cricket match—it was cricket versus the clock. An elderly spectator beside me put down his cup of tea and said, 'Brother, whether this match produces a result depends more on the weather than on bat and ball.' He was right. In this Ranji Trophy Elite Group C fixture at Eden, more than two sessions have already been lost to rain and bad light, and in between, Maharashtra were bowled out for 218 to take a 75-run first-innings lead. Bengal are 76/4 in their second innings—effectively just 1 run ahead, with six wickets in hand. The headline says 'Maharashtra take lead,' but the equation is far more complicated than that. This Ranji Elite Group C match was hostage to the weather from the start. Rain and bad light wiped out play on the first two days, and Day Three also lost sessions. In such a match, the value of a first-innings lead is greater than usual—because here it is not the runs but the remaining overs that matter. Eden's pitch is historically batting-friendly, but when the surface is damp and the sky overcast, seam movement can quickly change its mood. In my 22-year career I have seen Eden's 'mind games' many times—sometimes it gives batters heaven, sometimes it turns a seamer into an angel. That is what happened here. Maharashtra's first innings stopped at 218 after being 207/9—meaning the lower order added only 11 runs. But before that, Tanay Sanghavi's unbeaten 60, his maiden first-class fifty, pulled the team along. That innings gave Maharashtra a score above 200; otherwise they might have been bowled out for under 150. Bengal's first innings, however, does not come into this. The most decisive phase of the match was their second-innings top-order collapse—76/4 in a little over 10 overs. Mohammed Shami had Dadhe LBW in the first innings, but that was a lower-order batter. Bengal's real concern is their batting unit. Captain Abhimanyu Easwaran was caught behind in the fifth over. Sanghavi took two wickets in four balls—Gharami and Chatterjee. That four-ball, two-wicket spell turned the match. My experience tells me that in first-class cricket, such rapid wicket clusters are often caused by a spinner or seamer extracting help from the pitch, and the batters then fall victim to a 'condition-assisted' collapse. This is not proof of structural weakness, but rather a story of batters failing to adapt to a specific day's conditions. But I find the biggest story of this match elsewhere—how big really is the number 75? In a normal first-class match, a 75-run lead is moderate, routine. But here time has shrunk so much that this lead feels huge. Yet the number itself is not big—what is big is the lack of remaining overs. Without grasping this difference, the true picture of the match cannot be understood. Bengal are now effectively 1 run ahead, but they have six wickets in hand. If they add another 100-150 runs, Maharashtra will face a target of 100-150, which is not difficult to chase in a time-shortened match. But if Bengal are bowled out for 120 from 76/4, Maharashtra's target will be just 45-50, which they will chase easily. The equation has not tilted fully toward Maharashtra yet; if Bengal's lower order can fight back, the match will open up again. Now let me come to the angle no one is talking about. Many will want to see Sanghavi's 60 and his four-ball, two-wicket burst as the 'birth of a new star.' My advice: do not jump to that conclusion yet. This is his maiden first-class fifty, and no player's overall ability or future value can be judged on one innings. In my career I have seen many young players who blaze in one match and vanish in the next three. Sanghavi is probably a spin-bowling all-rounder, because two wickets in four balls in the 10th over is usually the spinner's work, especially when the pitch is damp and slow. But we have no data on his career average, strike rate, or home-away performances. So at this moment, calling him a 'discovery' is far less safe than calling him an 'emerging talent.' For Bengal, the worrying thing is the fragility of their top order. 76/4 at home, in their own conditions—this could be a one-off, or it could be a trend. When I watch matches from the stands in Dharamsala or Kolkata, I read not just the scorecard but also the empty seats. The Eden galleries were not full in this match—rain and bad light forced spectators to leave at times. But those who were there were clearly anxious. Messages from Bengal fans were coming into my WhatsApp group—'Easwaran is out, what now?' These messages tell you that Bengal's collapse at home has cracked the fans' confidence. Maharashtra's strategic advantage here is situational, not proof of overall team strength. They took the first-innings lead and will bat last—a classic winning position in a time-shortened first-class match. But I will say emphatically that Maharashtra have not proven themselves the 'stronger team' in this match. Rather, both teams' batting looked fragile in these conditions. Maharashtra stopped at 218 from 207/9, Bengal are stuck at 76/4. Both suggest that conditions are ruling this match, not any team's superiority. Now the biggest question—the weather. Will the match produce a result? The author says 'chances of a result are still high.' That is true, but fragile. If Eden's bad light and rain take away another session, this time-shortened equation will collapse toward a draw. I remember learning in 2026, while watching France vs Argentina with Bangladeshi fans in Russia, that 'Kazan taught me that a roar can travel farther than any passport.' Here at Eden, that roar has been stopped by rain. But outside the ground, the fans' heartbeat continues. One thing I noticed in this match—Shami's presence. An international-class pacer playing a domestic first-class match means he is trying to regain match fitness or is going through workload management. But in this match he took only one wicket, that too of a lower-order batter. Nothing can be inferred about his form from this. What matters for Bengal is that Shami does not bowl too many overs and stays fit for the next matches. And I must mention one more thing—Bengal's wicketkeeper-batter Abhishek Porel and Ankur Paul appeared in this match only as image subjects; there is no performance data on them. So it would not be right to speculate about their roles. In the end, the fate of this match will be decided by three things—the weather, the umpires' light meter, and the patience of Bengal's lower order. The number 75 sounds big, but it is not. It is a number inflated by time pressure. And Sanghavi's 60 is a beautiful story, but it is still a story of one innings, not a career. My notebook is always ready—because the real result of this match will be written not by bat and ball, but by the hands of the clock. If Sanghavi scores two more 40+ scores in the next round, then we can write stories about him. Not yet.