Rohit Sharma: In the match played on Monday night in the IPL, a decision of the third umpire has come under question. Rohit Sharma, neither the Mumbai players nor Rohit’s fans seemed to agree with the way Rohit Sharma was given out in the Mumbai Indians vs Kolkata Knight Riders match. In fact, Mumbai Indians, chasing the target of 166 runs, lost the wicket of captain Rohit Sharma in the very first over of their innings. The umpire standing in the field had given Rohit not out, but on the review of KKR, the third umpire indicated to send Rohit to the pavilion. Questions arose on this decision of the third umpire because Rohit was not seen getting out even in the review.
Tim Southee was bowling the first over from KKR. The last ball of his over, passing Rohit’s bat, hit the Thai pad and then went into the hands of wicketkeeper Sheldon Jackson. The players of KKR appealed but the umpire declared Rohit not out. KKR captain Shreyas Iyer took a review on this. In the review, the ball was seen touching the bat but in the ultra edge, a spike was seen while passing the ball and seeing this, the third umpire gave Rohit out. However, it was also clearly visible in the ultra edge that the spikes were visible even before the ball passed near the bat. So it could have been a technical fault. But the third umpire did not pay attention to it and declared Rohit out.
— Diving Slip (@SlipDiving) May 9, 2022
Rohit Sharma appeared to disagree with this decision. Soon after this decision of the third umpire, cricket fans started questioning this decision on social media as well. Someone said that Rohit Sharma was not out, then someone said that the ball did not hit the bat at all. Someone also said that in the ultra edge, the spikes were visible even before the ball came near the bat, here the umpire gave a wrong decision.
That was clearly not out. The ball didn’t even reach his bat. Lot of spikes before the ball reached his bat. Umpiring has been pathetic. It’s a shocker from Bruce Oxenford. #MIvKKR #RohitSharma https://t.co/23zrirN3C6
— Anirudh (@Anirudh_1901) May 9, 2022
— Jitendra Sharma (@Jitu_sharma45) May 10, 2022
— Sushant Mehta (@SushantNMehta) May 9, 2022
In this match, chasing the target of 166 runs, Mumbai Indians kept losing wickets at regular intervals and the entire team was all out for just 113 runs. This was Mumbai’s 9th defeat in this season.
IPL 2022 is proving to be the second worst season for Virat, the figures are giving testimony
CSK vs DC: Dhoni was seen chewing the bat while sitting in the dressing room, Amit Mishra enjoyed it like this