Eden Gardens Rain and Bengal's 76/4: A Case of a Dishonest Surface Filed in the Ranji Register

Wednesday afternoon, Eden Gardens. The first session was swallowed by rain. When play did begin, only 27.5 overs were possible in 3 hours 16 minutes. Bad light stopped play at tea. The scoreboard read Bengal 76/4 — an overall lead of exactly 1 run after erasing a 75-run first-innings deficit. To a T20 fan, that number means little. But in first-class Ranji Trophy cricket, 76/4 means the entire match structure is built on a slow, spinner-friendly surface — and that structure is now in the grip of the weather.

I have been filing this match into the Ranji registers for years. Since 2026, when I selected 14 boys out of 68 at a trial at the Eden Gardens indoor nets, I have viewed every innings through a date, a surface, and a session. This match is no different — a date (Wednesday, Day 3), a surface (Eden Gardens), and a session that washed away. So this report will lead with figures, move to analysis, and close with a clean verdict.

Maharashtra made 218 in their first innings. Bengal's first innings folded for 143 (218 minus the 75-run deficit). In the second innings, Bengal began at 25/3 — captain Abhimanyu Easwaran, Karan Gharami, and Sudeep Chatterjee all returned to the pavilion within a handful of deliveries. This is no coincidence. Easwaran chased an away-going ball and was caught behind; Gharami played across the line and was trapped; Chatterjee played on the rise and was bowled. Three different dismissals, but one root cause — against a moving ball, Bengal's top order failed on both technique and decision-making.

One clarification is essential, because Ranji data is often read through a T20 lens. Tanay Sanghvi made an unbeaten 60 off 179 balls — 3 fours, 1 six. His strike rate is roughly 33.5. In T20 that looks slow, but in first-class cricket it is entirely normal. Sanghvi's innings was the foundation of Maharashtra's 218, and on that foundation he took 2 wickets in 3 deliveries to break Bengal's top order. This is the match's standout all-round performance, and it must be read not as a single innings or a single spell, but against the full structure of the match.

Mohammed Shami's 4/37 is a strong first-class return in a low-scoring game. But the most important question in my register is not how many wickets Shami took. It is — why is Shami playing this match? An international bowler appearing in a Ranji fixture signals a workload management or comeback plan. That information is not in the original report, so I file it as 'inference,' not 'fact.' A 4/37 is a strong first-class figure, but treating it as proof of international readiness would be a category error.

Shahbaz Ahmed's 3/39 further strengthens his all-round profile — left-arm spin plus lower-order batting. In first-class cricket, such dual output is rare and valuable. But the real story of this match is not bowling — it is batting, or rather, the failure of batting.

Bengal's only relief came from Ankur Paul (32) and Abishek Porel (unbeaten, survived to tea). Paul shared a 49-run fourth-wicket stand that briefly steadied a crumbling fort. But stopping at 76/4 at tea tells us that partnership is not finished yet — and that is Bengal's biggest defensive weapon.

Now the most essential part of this report — the match's true master is the weather, not cricket.

Only 27.5 overs were possible on Day 3, the first session was entirely lost, and bad light stopped play at tea. DLS does not apply in first-class cricket. There is no revised target here, no over-reduction arithmetic. Only two variables exist — remaining time and weather. The direct implication is that despite Maharashtra's 75-run lead and Bengal's 76/4, a draw is the base case for this match. An outright result is the upside, requiring Maharashtra to bowl Bengal out quickly and chase a small target — and that requires clear weather on Day 4.

The group table stakes make this more interesting. Bengal are sole leaders of Elite Group 'C'. An outright win for Maharashtra would lift them to 18 points, level with Bengal. A draw for Bengal would keep them sole leaders with 1 point. That is why the remaining time is the most valuable resource in this match — and the two teams will use it differently. Maharashtra will want quick wickets; Bengal will want to eat time.

But one point is often lost in Ranji reporting — if Maharashtra win, it will be as much a product of Bengal's second-innings collapse as of their own superiority. And if Bengal save the draw, it will not prove batting strength — it will be a gift from the weather. Whatever the result, process must be read separately.

Now the angle that does not make headlines.

Headlines say 'Maharashtra put Bengal under pressure.' Technically true — 76/4 is a pressure score. But headline language is a snapshot, not a forecast. The real question is whether Maharashtra can convert that pressure into 18 points. That requires three things: clear weather, quick wickets, and the early break of the Porel-Jaiswal partnership. All three are uncertain.

A second angle, the biggest untold story of this match. Bengal's first innings folded for 143 — at Eden Gardens, their home ground. That figure tells us this pitch is not 'comfortable' for batters. Seam and spin are both getting help. In such conditions, Maharashtra's spin pair — Sanghvi and Hitesh Walunj — could be decisive on Day 4. Walunj had Ankur Paul caught at silly point, which tells us the surface is offering both bounce and turn. If Day 4 morning is clear, Maharashtra's real weapon will be their spin, not their pace.

A third angle, more relevant to selectors. Abhimanyu Easwaran's dismissal — chasing an away-going ball, caught behind — points to a technical vulnerability. This may not be a one-innings outcome but a pattern. Easwaran is being tracked for higher honours, and his decision-making outside off-stump is a trackable point. But I will not grade it a 'weakness' on one innings. It is a 'note,' not a 'conclusion.' In my register, this entry reads: 'Easwaran, away-going ball, keeper catch, Eden Gardens, Day 3 — monitoring continues, evidence insufficient.'

One more point, drawn from my 28 years of nets experience. In the winter of 2026, I watched a 15-year-old seamer bowl six overs at the Mohun Bagan nets — Mohammed Shami. I clocked his run-up at 12 yards and noted the seam staying upright past the 40th minute of the session. I did not push him into the senior side that year; I recommended 18 months of age-group cricket first. Today Shami is taking 4/37 in Ranji — the product of that same 24-month patience. That is why I never treat a single spell or a single innings as a 'verdict.' Porel's unbeaten innings matters, but it is one innings — not one season.

Now the part where I state my position clearly.

The biggest risk to this match is weather. If rain or bad light arrives on Day 4, the entire 'result' narrative washes away and a draw is certain. A second risk — treating Shami's 4/37 as 'international preparation' evidence. It is a first-class figure, nothing more. A third risk — treating Bengal's collapse as a 'permanent weakness.' One innings, one surface, one weather — that is not a trend.

So what next?

If Day 4 morning is clear, the first hour is worth watching — Porel and Suraj Jaiswal. If these two survive the first hour, Bengal's path to a draw opens. If Sanghvi and Walunj strike early, Maharashtra moves toward 18 points. But in my register, at this moment, the entry for this match reads: 'Eden Gardens, Day 3 — Bengal 76/4, lead 1 run. Surface: bowler-friendly. Weather: decisive. Result: uncertain, draw the base case.' 'The register does not lie; only the hands that forgot to write in it.' And in this match, the weather has left an entire session unwritten. Until that blank is filled, any conclusion is incomplete.

I will not close this file yet. I will reopen it after Day 4 — and then, whatever the result, I will write what the register says, not what the headline says.