Rain and Resistance at Eden Gardens: Maharashtra Turn the Screw as Bengal's Batting Falters Again

On Monday afternoon, a senior fan in the queue outside Eden Gardens told me, 'India plays three formats, but in Ranji, the weather plays the fourth.' I agreed with him. Covering the Ranji Trophy over the last few seasons, I have learned that the real story of domestic cricket is never on the scoreboard — it is hiding in the time the rain eats away. What unfolded in Kolkata on Wednesday is the latest reminder of that truth: Bengal are wobbling at 76/4, their overall lead against Maharashtra's 218 is just one run, and the entire first session was washed out.

To understand this match, you must first fix the format frame. This is not a Test. It is certainly not a T20 or an ODI. It is a four-day first-class encounter in Ranji Trophy Elite Group 'C', where a batting strike rate of 33 is entirely normal and a 4/37 return in a low-scoring game counts as a strong comeback. Anyone reading this through a T20 lens will call Tanay Sanghvi's 179-ball unbeaten 60 'slow' — when in first-class terms, that very innings is the story of Maharashtra's 218.

Maharashtra's match revolves around Sanghvi. His unbeaten 60 off 179 balls, studded with three fours and a six, anchored the visitors to 218 — a 75-run first-innings lead over Bengal's implied 143. With the ball, he took two wickets in three deliveries, dismissing Gharami and Chatterjee to break Bengal's top order. In first-class cricket, this is genuine match-shaping all-round value. I have watched the domestic game for two decades, and I can tell you that a 'grit' batter like Sanghvi — who knows how to leave the ball and occupy the crease — is always worth more in the longer format than his T20 valuation suggests.

Mohammed Shami's 4/37 is the biggest signal of the match, and I believe the figure itself is not the story — the bigger story is that Shami is playing Ranji cricket at all. An international fast bowler appearing in a domestic first-class fixture usually signals workload management or a return-from-injury process. He bowled for Bengal and, alongside Shahbaz Ahmed's 3/39, restricted Maharashtra to 218. Shahbaz's 3/39 reaffirms his left-arm spin plus lower-order batting combination — a dual contribution that is scarce and valuable in first-class cricket.

But the real story of this match lies in Bengal's batting struggle, and on a surface that did not behave like a home wicket. Captain Abhimanyu Easwaran fell chasing an away-going ball, caught behind — a technical vulnerability, not mere bad luck. Gharami and Chatterjee fell in the same passage as the score slipped to 25/3. Bengal's top order looked helpless on a surface where the ball was doing things, and the manner of their dismissals — chasing a moving ball, playing across the line, playing on the rise — tells you this is a decision-making problem, not just misfortune. Ankur Paul's 32, part of a 49-run fourth-wicket stand, was the innings' bright spot. Abishek Porel survived to tea with Suraj Jaiswal, and several members of my panel read that as Bengal's most important signal of the day — if Porel bats long on Day IV, the draw probability rises materially.

Now the angle nobody discusses enough: the group table's politics. Bengal are sole leaders of Elite Group 'C', and a Maharashtra outright win would lift them to 18 points and level with Bengal. A Bengal draw would fetch just one point but preserve sole leadership. That is why time has become the most valuable resource in this match — and the rain has taken exactly that away.

Here I face a familiar question from my panel: 'When it rains, who does the draw favour?' The answer is simple — rain always favours the team that is behind, because it buys them time. For Bengal, this rain is nothing short of a gift. But a gift does not make them a stronger team. If Bengal draw this match, it will not be proof of batting strength — it will be a reprieve from the weather. That is the distinction I keep underlining: the scoreboard is data, but the concourse is the real audit — and here the concourse is under rain cover.

So what should Maharashtra's strategy be? The first hour of Day IV is decisive. If the weather stays clear and Sanghvi and Walunj get some overs with the older ball, they can dispose of Bengal's remaining batters quickly. Bad light stopped play at tea — a signal that light, too, may be a constraint on Day IV, further reducing the result probability. Bengal, on the other hand, have only Porel and Jaiswal; if either falls in the first hour, the tail could buckle against spin.

One more thing I am tracking — and this is part of my reporting, not panel-washing — is Easwaran's technical situation. He is a batter tracked for higher honours, and his dismissal chasing an away-going ball can become a blueprint for opposing bowlers. Some of my Hyderabad Fan Desk members, who have tracked domestic cricket for years, say this pattern has repeated over the last few seasons. I am keeping it as a leading indicator, not a finding; proving it would require a full season of data, and a single match is not enough.

Finally, the biggest risk in this match is not defeat for either side — it is the weather. If rain arrives again on Day IV, the entire 'Maharashtra in control' narrative will reduce to a snapshot. In my experience, this is domestic cricket's biggest problem — Ranji scheduling alongside the monsoon, with matches losing their meaning to lost time. This is part of the ecosystem I call 'follow the money down the pyramid': where every IPL ball is broadcast, Ranji's decisive days are decided by clouds.

The question, then, is not whether Maharashtra will win. The question is whether the BCCI will treat domestic tournament scheduling and weather management with the same seriousness it brings to fixing the IPL window. Until that answer arrives, this Eden Gardens match will remain a weather department report, not a cricket story.