Rain Stops Play at Eden Gardens, Maharashtra Reduces Bengal to 76/4: What Is the Truth of the Struggle?

I opened the Eden Gardens scorecard and the first number that stared back at me was 27.5. That was the entire day's play. Three hours and sixteen minutes for 27.5 overs. That is the number that swallows whole any sentence about 'Bengal being under pressure' before it even leaves a fan's mouth. March 22, 2026, Wednesday. Ranji Trophy Elite Group C, fourth day, Bengal versus Maharashtra. The entire first session was washed out by rain. Bad light stopped play in the third. And when the umpires pulled the stumps, Bengal were 76/4 — an overall lead of just one run against Maharashtra's 218. If you look at the scoreboard and say Bengal are in trouble, you are not wrong. But if you say Maharashtra have won this match, you have not seen the rain that fell in the first session. Let us clear one thing before we read this match's structure: this is not Test cricket, it is a first-class Ranji Trophy fixture. Four days. The Duckworth-Lewis-Stern method does not apply here at all. Rain came, overs were cut, no target was revised. What was lost was time — and in first-class cricket, time is the biggest currency. That is why if you read this match through batting strike rates or bowling economy, you are reading a book whose pages have been bound in the wrong order. Tanay Sanghvi made an unbeaten 60 off 179 balls. If you look at that through T20 habits, it seems slow. A strike rate of 33 is entirely normal in first-class — that is the format's native currency. Sanghvi did exactly what an anchor is supposed to do: he carried Maharashtra to 218 while wickets fell around him. Now the part that gets ignored the most. Maharashtra made 218 in the first innings. Bengal's first innings folded for 143 (subtract the 75-run lead from 218 and that is what you get). The pitch was not easy for batting. Eden Gardens in Ranji matches offers seam early and spin later, and the manner of the wickets confirms it. Captain Abhimanyu Easwaran was caught behind chasing a ball going away. Gharami and Chatterjee fell in the same spell — 25/3. The ways they got out tell you the problem is technical, not merely bad luck. Chasing a moving ball, playing across the line, trying to stop a ball on the rise — all three point to a top order that was unstable in its decision-making against movement. I have no hesitation in saying Mohammed Shami's 4/37 is the biggest number on this scorecard but not the biggest story. The biggest story is that Shami is playing Ranji cricket. That is a signal of workload management or a comeback — and in my experience, that signal is the real document of national-team planning, not the 4/37. Look at the shape of Maharashtra's bowling. Pradeep Dadhe struck with the new ball, Tanay Sanghvi took two wickets in three deliveries, and Hitesh Walunj showed left-arm spin control by having Ankur Paul caught at silly point. This is the classic first-class template: the seamer breaks the top order, the spinner squeezes the middle. On a fourth-day pitch, as the wicket wears further, Maharashtra's spin pair will be Bengal's biggest threat. But here is the arithmetic I repeat on my podcast every time, and I will repeat it now: look at the points table. Bengal are sole leaders of Elite Group C. If Maharashtra win this match, they join Bengal on 18 points. Bengal get one point for a draw — but that one point keeps them sole leaders. That is the real stake. And that is why Bengal's aim will be survival, not victory. Now the part where I have to cut myself. I said above that Bengal's top order was technically unstable. That is true, but treating it as a firm conclusion off one innings would be my own impatience. This is a rain-hit match, a one-innings sample, on a pitch that did not let anyone past 218 in the first innings either. If I pronounce a permanent verdict on Easwaran's technique, I will commit the exact sin for which I scold TV commentators. On the other hand, I must also concede that the media's 'pressure' story has been slightly inflated. The headline says 'Bengal under pressure', and as a snapshot it is accurate. But if rain returns on the fourth morning, all that 'pressure' evaporates. A draw is this match's base case, not a Maharashtra win. My model, if I state it plainly, says the number of available overs is a bigger variable in this match than skill. And that is also my model's limit — it cannot forecast weather. So what will we see on day four? Abishek Porel and Suraj Jaiswal are at the crease. If this pair survives the first hour, Bengal's tilt toward a draw will rise sharply. Porel is a wicketkeeper-batter, and in my experience such batters prove most valuable in a crisis because they give the ball time. But if Sanghvi and Walunj take two more wickets in the first hour, the road to 18 points opens. My prediction, which I will grade myself in the next column: this match heads to a draw, and Bengal remain sole leaders. But that prediction rests on the mercy of the weather, and I accept that. I was in the stands at Eden Gardens in 2026, when the model had not even been invented. Today the model exists, but it cannot read rain. Perhaps that is the most honest truth of this game — and perhaps that is why I still prefer sitting in the stands, watching the scoreboard.