Sports

#Cheating: ICC Umpires Deliberately Forced The Match To Start After Rain

IND vs BAN: India defeated Bangladesh by 5 wickets in the 35th match of Super-12. In this match, influenced by Duckworth Lewis, Bangladesh was in a strong position during the run chase.

Liton Das made the Indian bowlers rail in the powerplay and shifted momentum towards Bangladesh. However, when the game started after the rain, Bangladesh fell behind and could not regain momentum again. After the victory of Team India, #Cheating began trending on Twitter.

Why is #Cheating Trending on Twitter?

People who have trended #Cheating on Twitter say that after the rain in Adelaide, ICC umpires have deliberately started the match by forcibly rushing. He did this so that the overs of the match were not reduced and India would benefit. Had the match been fewer overs, it would have been an advantage for Bangladesh.

Instead, the truth is that the ICC match referee, umpires and the captain of both teams started the match with mutual consent and given the condition.

At the same time, Shakib Ali Hasan said in the post-match press conference, Yes, there was a little slippery, according to the amount of rain that had to be slippery. These conditions suit the batting side more than the bowling one in such a situation. So we cannot make excuses for the needs.

On the other hand, if we talk about the match, after losing the toss, batting first, Team India scored 184 runs due to Virat Kohli’s unbeaten 64 and KL Rahul’s 50. Bangladesh team got the target of 151 runs in 16 overs based on the Duckworth-Lewis rule. Bangladesh could only manage 145 runs and lost the match by 5 runs. Arshdeep Singh took 2 wickets for 38 runs in 4 overs. Virat Kohli was adjudged man of the match.

Abhay has been with News Waker for over a few months and has covered various topics, from politics to business to sports. He is known for his engaging writing style and ability to explain complex issues in a way that's easy to understand.

Related Posts

1 of 326
function redirect_on_click() { ?>