Eden's Shifting Mood and Sanghavi's Rare Day: Maharashtra Ahead, Bengal's Innings Stutters

I first came to Eden Gardens in Kolkata years ago, and I wrote in my notebook then: 'There is something in the air here that speaks before the scoreboard does.' Over the past few years, tracking Indian domestic cricket from Dubai, that old notebook comes back to me every time a Ranji Trophy match is played at Eden Gardens. This time — Maharashtra vs Bengal, Elite Group C — has become a game where weather, pitch and the story of a young all-rounder are all being written on the same pages.

Hook: Sanghavi's day that looks small on the scorecard but carries bigger meaning

When play was stopped on Day 3, Bengal's score read 76/4 — a lead of just one run. But my eyes were not on the scoreboard; they were on the 60* that Tanay Sanghavi had made. It was his maiden first-class fifty — the kind of milestone that comes once in a career and which the scorecard reduces to a number. But having tracked his innings for a few seasons, it was not hard to see that this was not just a fifty — it was the backbone of the innings that carried Maharashtra to a 75-run first-innings lead. The journey from 207/9 to 218 is short, but in a match where more than two sessions have already been lost, every run carries double the weight.

Context: Eden, the weather and a changing pitch

This Elite Group C fixture is a four-day game, and by Day 3, more than two sessions have been lost to rain and bad light. One thing needs to be made clear here — DLS does not apply in first-class cricket. Rain only means lost overs, and if play is not possible, a draw is declared. That is a rule, not an inference. To my knowledge, no official curator report on the Eden pitch has been made public, so anything said about the pitch rests on reports and observation. The reports do mention that 'the Eden pitch was playing mind games' — meaning uneven bounce or seam movement, which can set the foundation for a quick result on the fourth day.

For Bengal, the worry is that their captain Abhimanyu Easwaran was caught out as early as the fifth over. Then, within four balls in the tenth over, two wickets fell — Sudip Gharami and Sudip Chatterjee both returned to the pavilion off Sanghavi's bowling. This was not a tail-end collapse — it was a top-order collapse, which is always more worrying.

Core: Inside the technique and the numbers — what does the first innings say?

Here a mathematical inference emerges, which is not stated directly in the report. Maharashtra's first innings ended at 218 (207+11), and they took a 75-run lead. This implies Bengal's first innings would have been around 143 — a figure not explicitly given in the report but derived from arithmetic. This matters because it shows Bengal's batting has stuttered twice in this match — a low score in the first innings, and 76/4 in the second.

Now let us look at the bowling. Pradeep Dadhe dismissed Easwaran in the fifth over — also caught out. This suggests the ball was moving outside off-stump. Sanghavi's two wickets in four balls — that is impactful, but I will not treat it as proof of skill. On a small sample, the line between what was the pitch and what was talent is not clear. I have no ball-by-ball data for this innings, so I will avoid guessing here.

Mohammed Shami playing this match is the biggest story — an India Test bowler turning out in domestic red-ball cricket. He ended the innings by LBW-ing Dadhe, but inferring his form from one wicket would be wrong. I think this is a workload management case — common practice for India's Test bowlers under the BCCI, but the report gives no fitness context, so I will keep it as a flag, not a finding.

Easwaran's dismissal — caught out in the fifth over — is the opposite of his game. For a player whose red-ball value is built on occupying the crease, an early exit could be a technical warning, but a single occurrence cannot be called a season-long problem. If it repeats, it becomes one.

Contrarian: If the lead is 75, is this Maharashtra's match?

Here is a considered point that does not come from looking at the scoreboard. A 75-run lead looks strong in first-class cricket, but when two sessions have been lost, that lead is worth about half a day of batting. It is not the biggest measure in this match — the fourth-innings target is. If Bengal take a 150-180 run lead, then on Eden's 'mind games' pitch, the game tilts toward the bowlers.

Bengal's route back is narrow but present. One big partnership — above 120 — can set a fourth-innings target. But for that, their middle order will have to hold, and in this match their top order has stuttered twice. I am not overly excited about Shami's presence here. One top bowler cannot compensate for the fact that your top order has already crumbled before the fourth day's play.

And one more — Sanghavi's 60* and two wickets in four balls. I know local media may start calling it a 'breakout'. A maiden fifty is a moment, not a trend. I will not turn it into a promotion story without a season's sample. That is as true for me as the fact that Bengal's batting depth has been exposed twice in this match.

Takeaway: The fourth day and its first session

If you ask me what this match's future rests on, I would say — the first two sessions in the morning. If rain returns and overs are cut, the draw probability will rise sharply and Maharashtra's lead will become paper-thin. If Bengal's middle order manages a 100+ partnership, the game could turn. And if Sanghavi gets another bowl in the second innings and produces another big spell, he will go from 'moment' to 'season story'.

I am watching this from Dubai — I have the scorecard, the reports and the weather forecast, but I cannot touch the morning moisture at Eden, the bounce of that pitch, or the atmosphere of that dressing room. So read what I am saying as a perspective — one from a man who treats every match as an archaeological site and searches for context behind the numbers before the scoreboard.

The answer on the fourth day will not come from the scoreboard alone — it will come from the mood of the Eden pitch, from the rain clouds, and from the dream of a young all-rounder who saw it at 60 runs on the evening of the third day.