Abhimanyu Easwaran’s promising 81 ended in unusual fashion on Thursday, the Bengal skipper wandering out of his crease for a drink just as the ball ricocheted off the bowler’s hand and on to the stumps. Services, alert to the situation, appealed; the third umpire confirmed the run-out.
It happened on the final ball of the 41st over in the sixth-round Ranji Trophy match at Palam. Sudip Chatterjee had driven a full delivery straight back to pacer Aditya Kumar. Easwaran, assuming the over had finished and that drinks were on, walked towards square leg, bat under his arm. Kumar’s fingertip deflection proved costly.
“The innings was going very well, but the mistake I made surprised even me,” Easwaran admitted afterwards. “Some might feel the opposition could’ve called me back in the spirit of the game, but there was no question of that. It was entirely my fault. I thought the bowler had collected the ball and instinctively moved forward.”
Laws and grey areas
Under Law 20.1, the ball remains live until both sides treat it as dead or the umpire calls “over”. Neither had happened. That makes the dismissal legal, if a little harsh on a batter in fine touch.
Coach Laxmi Ratan Shukla saw no controversy. “They may look similar, but you cannot compare the two directly,” he said when reporters raised Ian Bell’s 2011 Trent Bridge incident. “That was a different era and different circumstances. This was simply a mistake on the batter’s part. It doesn’t mean he lacks awareness; he is a senior player, but cricket can be unpredictable. While the opposition could have considered calling him back, but there is nothing wrong in their decision not to. Everything happened within the laws of the game.”
A reminder for batters
Players often switch off once a stroke is completed, especially if the fielding side appears relaxed. Yet until the umpire’s arm goes up or the ball is clearly dead, the onus is on the striker and non-striker to stay grounded. Ranji matches may not have the glare of international cricket, but lapses are still punished.
Impact on Bengal’s innings
Easwaran had looked set for what would have been his 28th first-class hundred. His dismissal left Bengal wobbling at 142 for 3, undoing a morning dominated by crisp drives and tidy rotation of strike. Chatterjee, who was 33 not out at the time, carried on cautiously, but Services sensed an opening and tightened their lines.
Perspective, not panic
Inside the dressing-room the reaction was calm rather than emotive. Easwaran’s form remains encouraging; his average this season is still north of 60. The run-out, while frustrating, counts as an individual lapse rather than a systemic issue. Bengal’s bowlers, who have carried the side in earlier rounds, will now need to restrict Services on a surface showing early signs of variable bounce.
For neutral observers, the episode serves as a timely nudge: cricket’s laws are precise but can feel unforgiving. And for Easwaran, a simple takeaway—finish the over, then fetch the water.
