Maharashtra's Grip on Eden's 'Mind-Games' Pitch: The Real Arithmetic Behind the 75-Run Lead and Bengal's 76/4
प्रश्न: महाराष्ट्र ने रणजी ट्रॉफी एलीट ग्रुप C में बंगाल के खिलाफ कितनी बढ़त हासिल की? उत्तर: महाराष्ट्र ने पहली पारी में 218 रन बनाकर बंगाल के खिलाफ 75 रन की बढ़त हासिल की, जिसके जवाब में बंगाल ने दूसरी पारी में 76/4 पर खेल समाप्त किया। मुख्य तथ्य: - महाराष्ट्र ने 207/9 से 218 तक पहुंचकर आखिरी विकेट के लिए 11 रन जोड़े। - बंगाल के कप्तान अभिमन्यु ईश्वरन पांचवें ओवर में कैच आउट हुए। - तनय संघवी ने 60* (पहला फर्स्ट-क्लास अर्धशतक) बनाया और दसवें ओवर में चार गेंदों में दो विकेट लिए। - मोहम्मद शमी ने प्रदीप दाधे को LBW आउट करके महाराष्ट्र की पारी समाप्त की। - बारिश और खराब रोशनी के कारण दो से अधिक सेशन बर्बाद हुए; फॉलो-ऑन की सीमा (200 रन) लागू नहीं हुई। स्रोत: PTI मैच रिपोर्ट, रणजी ट्रॉफी एलीट ग्रुप C, ईडन गार्डन्स, कोलकाता | Cross-checked: cricsultan.com संबंधित प्रश्न: प्रश्न: तनय संघवी का इस मैच में क्या योगदान रहा? उत्तर: तनय संघवी ने पहली पारी में 60* रन बनाकर टीम को संभाला और दूसरी पारी में दसवें ओवर में चार गेंदों के भीतर दो विकेट निकालकर बंगाल के टॉप-ऑर्डर को तोड़ा। प्रश्न: इस मैच में फॉलो-ऑन लागू क्यों नहीं हुआ? उत्तर: फर्स्ट-क्लास क्रिकेट में फॉलो-ऑन के लिए 200 रन की बढ़त आवश्यक है, और महाराष्ट्र की बढ़त केवल 75 रन थी, इसलिए यह नियम लागू नहीं हुआ।
At the close of Day 3 at Eden Gardens, two numbers clung to the scoreboard — Bengal 76/4, and the lead just 1 run. Between those two figures lies the whole story that has turned this Ranji Elite Group C fixture from an ordinary domestic game into a contest where the result is still very much alive. Maharashtra, resuming from 207/9, added 11 runs for the last wicket to reach 218 and secure a 75-run first-innings lead. Those 11 runs sound trivial, but in a match where more than two sessions have already been lost to rain and bad light, they are enough to tip the scales.

This match has been grappling with the weather from Day 1. Wednesday's rain and bad light on the first two days, plus the early hours of Day 3, have eaten into the playing time. DLS does not apply in first-class cricket — here overs are simply lost, and if time runs short, the match drifts toward a draw. But Eden's pitch has shown a character of its own through all this. The report describes it as a pitch that 'kept playing mind games,' and by Day 3 such a surface usually does not push toward a draw but accelerates toward a result. Uneven bounce and seam movement make life difficult for home batsmen on such a surface, and Maharashtra's pace attack has exploited that fully.
Bengal's second-innings collapse is no coincidence — it is a picture of a structural weakness in their top order. Captain Abhimanyu Easwaran was caught behind as early as the fifth over — and that is the strangest kind of dismissal for a player whose red-ball identity is built on occupying the crease. A catch behind means the hands went at a ball outside off, which points to instability against the off-stump line. A few overs later, in the tenth over, two wickets fell within four balls — Sudip Gharami and Sudip Chatterjee both departed cheaply. Losing the captain in the fifth over and two wickets in four balls points to two separate problems: top-three instability against the moving ball, and a vulnerable middle order.
This is where Tanay Sanghavi's story becomes the most important narrative of this match. Scoring 60* in the first innings to rescue the team from collapsing at 76 — that was his maiden first-class fifty, a personal milestone of its own value. But the real impact came in the second innings, when he took two wickets within four balls in a single over — the tenth — breaking Bengal's spine. This is the classic all-rounder profile: saving the team with the bat in one session and bringing the opposition to its knees with the ball in the next. But I must be careful here. A maiden fifty and a four-ball burst is a moment, not a trend. Concluding from this sample that Sanghavi is a next-level player would be the same mistake domestic cricket coverage makes again and again — declaring a career from one innings. The right question is: can he move the ball the same way in the next round?
Mohammed Shami's presence in this match is the biggest name in the whole narrative, and yet the least decisive fact. He ended the innings by trapping Pradeep Dadhe LBW — one wicket in a match where he was otherwise quiet. A seasoned fast bowler from the Test team playing a Ranji group game is a statement in itself — it could be part of BCCI's workload management, or practice to find rhythm ahead of the Test calendar. But one wicket is no measure of his form. Those who say Shami is 'back in rhythm' or 'struggling' will both be building a story beyond this single wicket.
Bengal's home advantage at Eden Gardens is generally considered a point in their favour. But when the pitch starts playing mind games, home advantage can backfire. On a surface where the ball is seaming, pressure mounts on the host team because they have to win in their own conditions. Maharashtra's pace attack understood this perfectly: the line and length Dadhe and Sanghavi maintained proved more challenging for Bengal's batsmen on this pitch. The direction of this match will no longer be decided by the lead alone, but by how big a target is set in the fourth innings. If Bengal's middle order cannot build a 120-150 run partnership, then even a 100-150 target will be challenging on Eden. And if Bengal manages to set a target of 180+, the game can turn completely.
The follow-on question never arose here, because a 75-run lead is far below the 200-run threshold. This is a direct consequence of the rule — Maharashtra does not have the right to invite Bengal to bat again, so the game is naturally moving toward a fourth-innings chase. This is the structure that makes this match interesting.

The biggest realization is that the result of this match may be decided more by weather than by cricket. More than two sessions have already been lost by Day 3, and the overs available on Day 4 are the biggest constraint. If rain or bad light returns on Day 4, the 75-run lead will mean nothing — the match will be drawn and Maharashtra's effort wasted. This is the biggest risk in an already time-shortened match, and it is a calendar and weather issue, not a cricket one.
One more thing is hidden in the reporting of this match — Bengal's first-innings score. It is not explicitly given in the report, but the arithmetic says that subtracting 75 from 218 (Maharashtra's total) puts Bengal's first innings at around 143. This is no small matter — scoring 143 in the first innings at home and then collapsing to 76/4 in the second says that Bengal's batting order is going through a deep crisis at the moment. This is not a one-match issue, but a signal for the whole season.
As for the 'size' of the lead, 75 runs matters in this context, but it is not a decisive figure in itself. In a time-shortened match, this lead is worth roughly 20-25% of a full day's scoring — material, but not commanding. The real decision will come from the target set in the fourth innings.
This Eden Gardens pitch has proven that even the Ranji Trophy has its own flavour of uncertainty. The first session of Day 4 will reveal whether Bengal's middle order struggles or writes a new chapter of resistance. If Bengal adds 120-150 runs, Maharashtra will face a target that will be big on this pitch. And if they collapse cheaply, victory will be a mere formality for Maharashtra. But first, check tomorrow's weather — because at Eden this time, the clouds are part of the game too.
