Shreyas Iyer Controversy in Ranji Trophy 2025: Umpiring Dispute Steals the Spotlight
The second day of the ongoing Ranji Trophy match between Mumbai and Jammu & Kashmir was marred by drama, with Shreyas Iyer at the center of a heated controversy. The incident occurred when Iyer, after scoring 17 runs, was declared out by the on-field umpire S. Ravi following a catch appeal off bowler Aaqib Nabi’s delivery. However, Iyer disagreed with the decision, leading to a prolonged argument on the field.
The Catch Controversy
Jammu & Kashmir pacer Aaqib Nabi bowled a delivery that reportedly edged Shreyas Iyer’s bat and was caught by wicketkeeper Kanhaiya Wadhawan, who dived to complete the catch. Despite the umpire’s ruling, Iyer believed the catch was not taken cleanly and refused to walk off immediately. Ajinkya Rahane, the Mumbai captain and non-striker at the time, also expressed his dissatisfaction and engaged in a discussion with the umpire. However, after a lengthy deliberation, umpire S. Ravi upheld his decision, forcing Iyer to return to the pavilion visibly upset.
Recurring Tensions with Umpire S. Ravi
This isn’t the first time Shreyas Iyer and umpire S. Ravi have been involved in a controversial incident. During a previous match between Mumbai and Jammu & Kashmir, another catch appeal against Iyer led to heated exchanges. In that instance, Iyer was batting on 8 runs when the Jammu & Kashmir players appealed for a catch out, convinced that the ball had touched his bat. However, the umpire ruled in Iyer’s favor, sparking anger among the opposing team.
Mumbai’s Fightback: Shardul Thakur’s Heroics
Mumbai’s innings, which started on a shaky note, was stabilized by a remarkable performance from Shardul Thakur. The team was struggling at 101/7 when Shardul, alongside Tanush Kotian, staged a recovery. Shardul scored an impressive century, amassing 113 runs off 119 balls, including 17 boundaries. Tanush Kotian also contributed significantly with a gritty half-century, scoring 58 runs off 119 balls with six fours. Their partnership propelled Mumbai to 274/7 after 67 overs, giving them a lead of 188 runs.
Mumbai’s Top Order Struggles
Mumbai’s top-order batters failed to deliver in both innings. In the second innings, Rohit Sharma was dismissed for just 28 runs, Yashasvi Jaiswal managed 26, Ajinkya Rahane scored 16, and Shivam Dubey went out for a duck. The first innings was even more disappointing, with Rohit scoring just 3 runs, Yashasvi 4, Rahane 12, Iyer 11, and Dubey once again dismissed without scoring.
Looking Ahead
Despite Mumbai’s lead, the controversy surrounding Shreyas Iyer’s dismissal and the recurring disputes with umpire S. Ravi have overshadowed the game. With Shardul Thakur and Tanush Kotian keeping Mumbai in contention, all eyes will now be on Jammu & Kashmir’s response in the upcoming innings.
