0

On Rohit Sharma Batting 2nd Time In Super Overs, Afghan Star’s Blunt Response

Rohit Sharma in conversation with umpire in 3rd T20I© BCCI/Sportzpics




The third T20I between India and Afghanistan was an absolute nail-biter that saw the hosts emerge triumphant after two Super Overs were bowled. With this being the first instance in an international match where two Super Overs were bowled, certain rules were ‘overlooked’ as India captain Rohit Sharma came out to bat in the second Super Over after being ‘retired out/retired hurt’ in the first. While no official complaints were made by any Afghanistan player during the match, Karim Janat has now said that Rohit shouldn’t have been allowed to bat again.

With just one ball to go in the first Super Over, and India needing 2 runs to win, Rohit returned to the bench retired (out or hurt). But, after the Super Over ended in a tie, the India skipper came out to bat again, prompting a debate about whether he should’ve been allowed to or not.

“We didn’t know much about that. Our management talked to the umpires. Rohit came out to bat, but we learned later that he shouldn’t have been allowed to do that. Even if you were retired out, you can’t come to bat again. We can’t do much about it now because what’s happened has happened. The captain and coach discussed about it later, but it was all between them,” Janat told Hindustan Times.

As far as the rules are concerned, Rohit shouldn’t have been allowed to come back if he was retired out, but was eligible to bat again, if he was retired hurt.

After the match, Afghanistan coach Jonathan Trott said that he had no idea about Rohit’s situation.

“I have no idea (whether Rohit retired hurt or out). Has there ever been two Super Overs? That’s what I am trying to say. We keep setting these new rules. What I am trying to say is we kept testing the rules, we kept testing the guidelines,” Trott had said in the post-match press meet.

Topics mentioned in this article

#Rohit #Sharma #Batting #2nd #Time #Super #Overs #Afghan #Stars #Blunt #Response