Maharashtra Hold the Edge at Eden Gardens, but Weather Remains the Biggest Player

The light at Eden Gardens had fallen so low that the difference between the green outfield and the red ball was beginning to blur. Bengal were 76 for four in their second innings, only one run ahead of Maharashtra. The players were still on the field, but the clouds and bad light appeared to be exerting as much influence as the bowlers.

Maharashtra had moved from 207 for nine to 218 all out, adding 11 runs for the final wicket. That small stand gave Maharashtra a 75-run first-innings lead. In an ordinary four-day match, it would be useful but hardly decisive. After more than two sessions had been lost to rain and bad light, its value changed. This was now a contest shaped by the amount of cricket left to play.

The match context

This is a Ranji Trophy first-class fixture, not a Test or a limited-overs match. Both teams have two innings, and the time available is central to the result. Maharashtra’s lead was below the standard 200-run follow-on threshold, so Bengal had to bat again. There was no possibility of Maharashtra enforcing the follow-on.

Bengal’s second innings began badly. Captain Abhimanyu Easwaran was caught behind in the fifth over. Two more wickets fell within four balls in the tenth over, leaving Bengal four down for 76 and only one run ahead. That points to serious pressure on the top order in these conditions, although one innings cannot establish a season-long technical weakness.

The report describes the Eden Gardens pitch as playing mind games. That may indicate movement off the seam, inconsistent bounce or uneven carry, but no formal pitch report or ball-by-ball data is available. The safest conclusion is that early mistakes are being punished heavily. Rain on Wednesday and bad light on the first two days have further compressed the game.

Unlike a limited-overs match, first-class cricket does not use the Duckworth-Lewis-Stern method to create a revised target. If rain returns, the match simply loses playing time. That makes the fourth day’s weather the most important factor outside the players’ control.

Sanghavi’s two decisive moments

Tanay Sanghavi has been the match’s most influential player so far. He made an unbeaten 60, his maiden first-class fifty, while rescuing Maharashtra from 207 for nine. His 11-run last-wicket stand helped establish the 75-run lead.

He then struck with the ball, taking two wickets in four deliveries during the tenth over of Bengal’s second innings. That burst prevented Bengal from building early momentum. In first-class cricket, matches often turn through small passages: a last-wicket stand of 11, followed by four deliveries that remove two top-order batters.

The performance should still be read carefully. A maiden first-class fifty is an important career milestone, but it is not evidence of established batting quality. Two wickets in four balls demonstrate impact, yet the available information cannot separate Sanghavi’s skill from the assistance provided by the surface. His next few matches will tell us whether this was the start of a pattern or an exceptional day.

Pradeep Dadhe also made a significant contribution for Maharashtra. He dismissed Easwaran behind the wicket and later removed the last batter of Maharashtra’s first innings leg before wicket. Mohammed Shami ended Maharashtra’s innings with that dismissal. Shami’s presence naturally attracts attention, but one wicket is too little evidence to judge his form, workload or fitness.

Why the lead and wickets matter together

Maharashtra’s advantage is not simply a 75-run lead. It also has four Bengal wickets. In first-class cricket, that combination is often more valuable than the lead alone because Bengal must first erase the deficit and then create a target for the fourth innings.

Bengal need one substantial partnership. A stand of roughly 120 runs could change the match, potentially establishing a fourth-innings target in the 180-to-220 range. On a difficult surface with limited time, that would be competitive. If Maharashtra take two or three more wickets early on the fourth day, Bengal may be unable to build any meaningful target.

Based on my years of watching first-class matches, the scoreboard rarely tells the entire story through the lead alone. The more useful questions are how the lead was created, how many wickets fell afterward and how much time remains for a chase. Maharashtra’s 75-run advantage is not conclusive, but calling it minor would also be misleading. It has transformed Bengal’s second innings into a reconstruction exercise.

Easwaran’s early dismissal is especially interesting. His red-ball value is built around occupying the crease and wearing down the new ball. An early edge behind is the opposite of that method. One dismissal cannot become a technical verdict; repetition would be needed before treating it as a genuine weakness.

The counterintuitive angle: Shami’s name versus Maharashtra’s work

Much of the attention around this fixture may settle on Mohammed Shami, the experienced India Test bowler playing for Bengal. Yet the match has so far been shaped less by reputation than by Maharashtra’s collective execution. One high-profile wicket-taker cannot cover a top order that has fallen to 76 for four.

Maharashtra’s bowling story is also broader than Sanghavi’s burst. Dadhe provided the early breakthrough, Sanghavi intensified the pressure and Bengal were denied the time needed to form a partnership. On a difficult pitch, a bowling unit does not need to threaten a wicket with every delivery. It needs to make the next mistake increasingly likely.

The available data also has clear limits. Bengal’s first-innings total is not stated, although the figures imply a score of approximately 143. That is an arithmetic deduction, not an independently verified scorecard fact. There is no toss information, no dropped-catch detail, no official pitch report and no points-table context. This match cannot support claims about Bengal’s entire season or Maharashtra’s title prospects.

Maharashtra are in the stronger position, but the weather is against certainty. Prolonged rain or bad light on the fourth day could neutralise the lead and produce a draw. Weather has become part of the match calculation rather than a background inconvenience.

What happens next

Bengal’s route back is narrow but open. The middle order must produce one substantial stand, after which Shami and the rest of the attack will need to defend a meaningful target. Maharashtra need wickets, especially in the opening session, and the eventual target will determine the final balance.

Some careers turn on moments that the scorecard records in a single line. For Sanghavi, an unbeaten 60 and two wickets in four balls could become such a moment, although only consistency will turn it into a larger story. The central question at Eden Gardens is no longer simply how many runs Maharashtra lead by. It is how many hours the fourth day will provide—and whether Bengal can use them to build a partnership before Maharashtra’s attack opens the match completely.