Rain, Bad Light and a Fading Home Advantage: Maharashtra's 75-Run Lead Against Bengal at Eden Gardens

The Eden Gardens pitch was asking more questions of its own home side than of the visitors by the end of Day Three. Maharashtra had extended their overnight 207/9 to 218, securing a first-innings lead of 75 runs — a margin that looks modest on paper but becomes a different story entirely in a match where more than two sessions have already been lost to rain and bad light. By stumps, Bengal's second innings had collapsed to 76/4, a lead of just one run. Captain Abhimanyu Easwaran was caught behind in the fifth over, and two wickets fell within four balls in the tenth — Sudip Gharami and Sudip Chatterjee both back in the pavilion. This was not just a bad day for Bengal; it was a direct question about the batting depth of a team struggling at its own ground against an opponent widely considered the underdog. This is a Ranji Trophy Elite Group C fixture — four-day red-ball first-class cricket where each side bats twice and a result remains the norm. Ranji group matches award bonus points for outright wins, so home teams rarely play for draws. The problem here is that more than two sessions across three days have already been swallowed by darkness and rain. If Day Four also starts late, the biggest threat to this match is not cricket but weather. The Eden pitch has also shown uneven bounce on Day Three — some deliveries have stopped on the batsman, others have kicked up unexpectedly. When a large target is set in limited time and the pitch is playing double games, the pressure on the bowling side multiplies. That is exactly the pressure Maharashtra's attack — Pradeep Dadhe and Tanay Sanghavi — has applied to Bengal. Dadhe provided the early breakthrough, and Sanghavi took two major wickets within four balls to leave the innings in tatters. Maharashtra's first innings had resumed at 207/9 and ended at 218. The last pair added 11 runs before Dadhe was trapped LBW by Mohammed Shami. Those 11 runs are a small number, but when an entire match is affected by rain and bad light, every run carries added weight. Had the innings ended at 207, the score would have been 64; the final total of 218 was enough to put psychological pressure on Bengal. Tanay Sanghavi's unbeaten 60 was the most valuable contribution of the innings — his maiden first-class fifty. For a young player, a first half-century can come in any innings, but when it arrives in a match where the team is reeling at 207/9, its significance multiplies. With the ball, he then took two wickets in four balls to prove he is becoming the most decisive player in this match as an all-rounder. Caution is warranted, however — a maiden fifty or a four-ball burst is a moment, not a trend. Bengal's biggest concern is their top order. Abhimanyu Easwaran, the captain and a long-format specialist, was caught behind in the fifth over, edging to the keeper. This is not the dismissal pattern he is known for — his value is built on occupying the crease and wearing down the bowling. An early edge behind is a warning sign for any opener, especially when seam movement is present. After him, Sudip Gharami and Sudip Chatterjee both fell within four balls in the tenth over. This raises questions about both Bengal's batting depth and their ability to adapt to the pitch. It is important to understand what Bengal scored in their first innings. The report does not state it directly, but the arithmetic is clear — if Maharashtra made 218 and secured a 75-run lead, Bengal's first innings must have folded for approximately 143. That number alone tells the story: Bengal's batting has failed twice in the same match — a low first-innings total and now 76/4 in the second. This is not just one bad day; it points to a structural flaw in the batting order. In domestic red-ball cricket, if your top three or four batting positions fail twice in the same day, it is a problem at both technical and mental levels. Mohammed Shami's presence is the most discussed aspect of this match. An India Test regular playing a Ranji group game is a significant story in itself — it could be part of workload management or a tune-up ahead of the Test calendar. But his contribution in this match was limited to one wicket — the LBW of last man Dadhe. Judging a bowler's form from a single wicket would be wrong, especially when rain and bad light gave him limited opportunities to bowl. Shami's real test will come on Day Four, when Bengal need six wickets and Maharashtra need to prevent a 120-180 partnership. The behaviour of the Eden Gardens pitch is the biggest uncertainty in this match. The report says the pitch was 'playing mind games' — uneven bounce and seam movement forcing batsmen to think constantly. By Day Three, such conditions usually push the game toward a result, because when bowlers are getting help from the surface, big partnerships become difficult. Maharashtra's seamers — Dadhe and Sanghavi — are finding the pitch to their liking. For Bengal's batsmen, the same pitch is creating problems. This is the home-ground factor that is often overlooked — the host team is familiar with the pitch, but when the pitch starts playing tricks, that familiarity can become a disadvantage. Looking at Bengal's 76/4 in the second innings, it is easy to assume Maharashtra have a firm grip on the match. But a basic first-class rule applies here — with a 75-run lead, the follow-on threshold of 200 is irrelevant. This means Bengal had to bat again, and now Maharashtra will chase a target in the fourth innings. This is where the match's real turning point will come. If Bengal's middle order produces a big partnership — 120 to 180 runs — Maharashtra will face a target of 180-200 on a difficult pitch. If Bengal collapse quickly, Maharashtra will have a small target and will likely win. The time already lost to rain and bad light is a major factor in itself. More than two sessions have been wasted. If Day Four does not start on time or is interrupted, the draw probability will rise sharply. That would be a scenario where Maharashtra's 75-run lead yields no advantage. First-class cricket does not use DLS — rain reduces overs, and if no result is possible, the match is drawn. That is a rule, not an inference. If the weather interferes again on Day Four, this will be a story of a team that played better cricket but did not get a result. Another factor that makes this match interesting is the Ranji Trophy points table context. The Elite Group C standings are not available, but if Bengal need an outright win for qualification, their fourth-innings approach will change. If they only need a draw, they can play defensively. But at 76/4, even a defensive approach is not easy. Bengal have only one route from here — a long middle-order partnership to set Maharashtra a respectable target. Tanay Sanghavi's story is the most compelling narrative of this match. Scoring an unbeaten 60 in the first innings to rescue his team, then taking two wickets in four balls in the second — this is a performance that can reshape a young player's career. But declaring a player a future star on the basis of one match would be premature. His maiden fifty is a milestone, not a trend. His performances over the next few innings will determine whether this was a one-day spark or the beginning of something substantial. The real question for Bengal is how long their top order can keep stumbling. A first-innings total of around 143, then 76/4 in the second — a pattern is forming. Easwaran's dismissal in the fifth over is a personal concern for a player whose role in the long format is to anchor the innings. If he keeps getting out early, it will signal a need for technical adjustment. One innings is not enough to draw conclusions, but if the pattern repeats over the next few innings, it will become a serious issue. Day Four will answer several questions. Maharashtra need six wickets and do not have much time. Bengal need to salvage their second innings and set Maharashtra a challenging target. If Bengal reach 250, a 175-run target could be difficult for Maharashtra because the pitch is helping bowlers. If Maharashtra bowl Bengal out for 150, they will have an easy 75-run target. Through all of this analysis, one thing is clear — this match is not over. Despite Maharashtra's 75-run lead and Bengal's four wickets down, the result could go either way. The time lost to rain and bad light could work for or against Maharashtra. If Day Four produces a full day's play, Maharashtra are the favourites. If rain returns, the match will drift toward a draw, and Maharashtra's lead will count for nothing. What happens on the next morning at Eden Gardens will not just decide this match's result — it will also reveal how deep Bengal's batting is this season and how steady Maharashtra's bowling attack is. For Tanay Sanghavi, this match could be the biggest day of his career. For Bengal, it will leave a question they must answer over the next few weeks. And for Shami — this is just a Ranji match, but every signal about his fitness and form matters to the Indian Test team.