Maharashtra Tightens Grip on Eden's 'Mind-Game' Pitch: Sanghavi's Maiden Fifty and Two Wickets in Four Balls Leave Bengal Reeling at 76/4

At Eden Gardens in Kolkata, when the day's play began, the 76/4 on the scoreboard was not the shocking part — the shocking part was that this was the score of the home team, a team with Mohammed Shami in its ranks, batting on its own soil with a lead of just one run.

Day three of this Ranji Trophy Elite Group C fixture against Maharashtra dawned as a morning that seasoned followers of domestic cricket recognise: the pitch is aiding the bowlers, the sky is not clear, and the visiting team's seam bowler is on the right line with the new ball.

This report opens at the point where Maharashtra ended their first innings at 218 — the last pair added 11 runs before Pradeep Dadhe was trapped LBW by Shami. Those 11 runs took Maharashtra's lead from 64 to 75. That seemingly ordinary margin is extraordinary in this match, because two sessions have already been lost to rain and bad light, and every run carries double weight.

Bengal's second innings began and in the fifth over, captain Abhimanyu Easwaran was caught behind. That wicket went to Dadhe. In the tenth over, Tanay Sanghavi struck twice within four balls — Sudip Gharami and Sudip Chatterjee both departed within four deliveries. Bengal thus lost four wickets for just 75 runs, and at stumps the score was 76/4 — meaning Maharashtra's overall lead was just one run.

The phrase 'the pitch kept playing mind games' comes back to me in domestic cricket when a surface suddenly changes character on the third day. What Eden Gardens' pitch did in the first two days is not clear from the report — no curator's report, no toss information, no detail of the first innings batting order. But one thing emerges from arithmetic: if Maharashtra's first innings ended at 218 and the lead is 75, then Bengal's first innings folded for approximately 143. This is inference, not hard fact, but it points in a clear direction — the home team's batting has stumbled twice on this pitch.

Now the most important part of day three's play: Tanay Sanghavi. An unbeaten 60 in the first innings — his maiden first-class fifty — and then two wickets in four balls with the ball. In domestic cricket, this is the profile that IPL scouts write in their notebooks, but it is also the trap they fall into most often. A maiden fifty is a career milestone, not proof of form. Two wickets in four balls is impact, not proof of skill — because it is impossible to determine how much was the pitch and how much the bowler.

The biggest name in this match is Mohammed Shami, and that is this report's biggest silence. An India Test team's premier fast bowler playing a Ranji group match is news in itself — is this part of workload management, a return-to-play pathway, or merely a domestic availability window? The report gives no indication. Shami took the last wicket, that is all. Inferring form from one wicket is the mistake television panels make every evening.

One fact needs clarifying here that often goes missing in domestic cricket debates: the follow-on rule. Maharashtra's lead is 75, far below the 200-run threshold. This means Bengal must bat again — there is no option. The structure of the match has now shifted towards a fourth-innings target, and that is the real question: on this 'mind-game' pitch, how much of a target is safe?

My estimate is that any target above 180-200 on this pitch will tilt towards the bowling side. Bengal need a partnership of at least 120-150 in their second innings, only then can they put Maharashtra under pressure in the fourth innings. But this hope rests on a team whose top order has already collapsed twice in this match — the captain in the fifth over and two batters within four balls.

Here is what the scoreboard does not tell you: Bengal's real problem is not the pitch, it is their top three. One innings collapse can be coincidence, but two collapses in the same day is a signal. Easwaran's dismissal caught behind in the fifth over is the opposite of his game — for a batter whose red-ball identity is built on occupying the crease, an early edge behind is a technical concern, if repeated. In a single occurrence it is merely an event, not a trend. But in the context of the season, it is the flag Bengal's selectors should be watching.

Maharashtra also hold the psychological edge in this match. A 75-run lead and four wickets — in first-class cricket, 'lead plus wickets' is the strongest direct indicator of victory. But here I would add a caution, because it is my biggest habit: this is a picture of one match, not a season. The report has no Group C points table, nor any team's season record. So saying 'Bengal are in crisis' or 'Maharashtra are contenders' would be a leap beyond the data we have.

The same caution applies to Shami. His presence does not make Bengal favourites. One world-class bowler cannot compensate for a top order that is failing repeatedly on the third day, with time already lost. And if I am to be completely honest, the biggest risk attached to Shami in this match is not the result, it is his fitness. An injury to an India Test bowler in a domestic group match would be a bigger story than the result. The report has no fitness information, so this is a warning, not a finding.

The role weather has played in this match comes from the rulebook. DLS does not apply in first-class cricket — if it rains, overs are lost, and play stops at the end of the day. More than two sessions are already gone, meaning the available overs on day four are the real constraint. Bengal have a narrow but real path back; Maharashtra have the lead but limited time. The first session of day four will decide whether this becomes a 'result' or a 'rain saved us' story.

And here is one thing that always bothers me when I watch domestic cricket. We are quick to call a maiden fifty a 'breakout' and turn a four-ball two-wicket burst into a 'sensation'. Sanghavi's day has genuinely been excellent — rescuing the team in the first innings and holding the fort with the seam in the second. But do we know whether he is a seamer or a spinner? The report does not say. Do we know under what circumstances his first-innings score was made — how many wickets had fallen, who was bowling? No.

So for now, this is the conclusion: this is a match where a result is most likely, but not for the reason the scoreboard suggests. The real reasons are — a pitch changing character on the third day, a home team whose top order is helpless against that character, and a visiting team whose all-rounder has emerged at precisely the moment of greatest need.

Watch tomorrow's first session — if Bengal put together a 100-run partnership, Maharashtra's 75-run lead will suddenly look very small. And if Sanghavi takes the ball again in the morning, the question will not be how many wickets he takes — it will be whether we see him on this pitch again next season, or in an IPL auction list. In domestic cricket, the distance between talent and opportunity is often more than one good day.