Rain-Shortened Day Three: Maharashtra Reduce Bengal to 76/4, but Weather Still Shapes the Result

Rain took the entire first session away from Wednesday’s third day at Eden Gardens. When play resumed, Maharashtra’s task was no longer simply to take wickets; it also had to make the remaining time work in its favour. By the close, Bengal were 76/4 and had erased the first-innings deficit to lead by just one run. Maharashtra had made 218 in its first innings, securing a 75-run advantage. The scoreboard showed pressure. The calendar showed how quickly the opportunity to turn it into a result was shrinking.

Rain washed out the morning session. Only 27.5 overs were bowled after play resumed, and bad light stopped proceedings at tea. In a four-day Ranji Trophy match, lost time directly affects the chance of a result. Unlike limited-overs cricket, the first-class game does not use the Duckworth-Lewis-Stern method to reset a target after rain. The key variables are the time remaining, wickets in hand and the first-innings lead.

This is a Ranji Trophy Elite Group C first-class fixture, not a Test match. In this format, patience across an innings, pressure built session by session and enough time to dismiss the opposition twice all matter. Maharashtra’s 75-run first-innings lead gave it a genuine advantage, but the lost third-day time makes that advantage harder to convert into victory. The available figures imply Bengal’s first-innings total was 143, 75 fewer than Maharashtra’s 218. That low score suggests Eden Gardens has not been an easy batting surface.

Maharashtra created pressure with the ball, but control of the match now depends on its contest with time as well. Early wickets in Bengal’s second innings put the visitors in a strong position. Captain Abhimanyu Easwaran chased a ball moving away from him and was caught behind. Gharami and Chatterjee fell soon afterwards, leaving Bengal at 25/3. The manner of those dismissals matters: poor fortune alone did not account for the top-order damage; decisions against movement and bounce also contributed.

Mohammed Shami took four wickets for 37 runs in the first innings. In a low-scoring first-class game, that is a strong return, though one match cannot establish a player’s availability or readiness for a higher level. His appearance in this Ranji fixture is worth monitoring, but the available information does not confirm an injury comeback or a workload-management plan. The evidence on the field—four wickets—is clear; any further explanation needs separate confirmation.

Shahbaz Ahmed contributed three wickets for 39 runs. His return helped Bengal’s attack, while spin came into view in Maharashtra’s second innings. Tanay Sanghvi made an unbeaten 60 from 179 balls in Maharashtra’s first innings, with three fours and a six. A strike rate of about 33.5 is not unusually slow in first-class cricket. His innings mattered less for its pace than for the time and resistance it supplied on the way to Maharashtra’s 218.

Sanghvi then struck with the ball, dismissing Gharami and Chatterjee within three deliveries. That is the match’s most consequential individual sequence: a long first-innings contribution followed by wickets when Bengal were under pressure. Sanghvi’s all-round impact gave Maharashtra both a lead and momentum. With the new ball, Pradeep Dadhe dismissed Easwaran; in the middle order, Hitesh Walunj had Ankur Paul caught at silly point. Maharashtra used both methods—pace against the top order and spin to create a close-catching opportunity—to keep Bengal under pressure.

Paul’s 32 was the clearest resistance amid Bengal’s early collapse. A 49-run fourth-wicket stand steadied the innings briefly, but Bengal’s advantage came under renewed pressure when that partnership ended. Wicketkeeper-batter Abishek Porel and Suraj Jaiswal were unbeaten at tea. Bengal’s task is now to add runs while also consuming time. If Porel stays in and the partnership grows, the remaining hours may run out before Maharashtra can set up a second-innings chase.

The match’s less visible decisive resource is not runs but overs. Read on its own, Maharashtra’s first-innings lead and Bengal’s 76/4 make the visitors look firmly on top. But only 27.5 overs were possible on the third day, and bad light ended play early. Maharashtra must first dismiss Bengal, then establish a target, and still have time to chase it or take the remaining wickets. Each stage requires overs; rain has reduced that available capital.

The group table makes the time constraint more significant. According to the available information, Bengal are the sole leaders in the group. An outright Maharashtra win would take the visitors to 18 points and level with Bengal. A draw would give Bengal one point and keep them alone at the top. Maharashtra therefore need to turn their advantage into a win; Bengal can focus on preserving wickets and using up the available time rather than building a large total. The teams now have different priorities.

This is where the headline narrative has a limit. “Maharashtra put Bengal under pressure” accurately describes the third-day score, but it does not forecast the result. Bengal’s batting failure is real, yet one innings cannot establish a season-long technical weakness. Maharashtra’s bowling has created opportunities, but the weather is against its push for a result. The figures show that Bengal will have to answer for its top-order failure; they do not show whether the fourth day will provide enough time to do so.

Based on my years of watching first-class matches unfold session by session, a poor half-hour can dismantle an innings, while losing an entire session can leave even a good bowling plan unfinished. Weather has not replaced skill in this contest, but it has narrowed the opportunity to convert skill into a result. Maharashtra’s advantage is concrete; its control is not yet decisive.

If the weather clears on the fourth day, the spin of Sanghvi and Walunj could be Bengal’s hardest test. If Porel and Jaiswal get through the opening hour, the draw becomes more likely; renewed rain or poor light could push the match further from a result. Which will shape the next session more decisively: the first partnership or the first weather update?