IPL 2022, RR vs MI | Twitter erupts as Tim David drops a ‘sitter’ at deep backward point
no image
186
Mumbai Indians (MI) had an average start against Rajasthan Royals (RR) in Match 44 of the ongoing Indian Premier League (IPL) at Dr DY Patil Sports Academy, Mumbai. RR, after Rohit Sharma won the toss and asked them to bat, had a steady start, scoring 15 off the first 15 balls. It largely came duo to back-to-back fours by Devdutt Padikkal, against Daniel Sams in the third over.
The fourth ball, bowled by Sams, was short and wide ball outside off. Padikkal tried to slash it over off-side, but the protection was there in Tim David at the deep backward point. However, the ball bursted through David's hands, largely due to his laziness, and eventually, it resulted in hat-trick of fours.
Although Padikkal did not make the best use of the lifetime, as he fell to Hrithik Shokeen in the fifth over after scoring 15 off 15 balls. RR, with the dismissal, reached 37/1 at the end of five overs.
DROPPED!
— James Tyler (@JamesTyler_99)
TOTALLY!
Tim David already contributed
— Deepansh Rajput (@DeepanshRajput4)
NOT TRUSTING ANYMORE!
The Mumbai Indians players don’t trust Tim David in the field 🤐💀
— chad (@Roamingbushman)
PATHETIC!
Yea..or else we would have won that First match and things would have been so different..Pathetic Tim David
— mogambokushhua (@mogambokushhua3)
NOT A CUP OF TEA!
Tim David Should Play Just As A Batter. Fielding Is Not His Cup Of Tea.
— Oggy #WhistlePodu 💛 (@SirOggyBilla)
SUMS UP!
That dropped catch from Tim David sums up the for
— Vikass (@vikas_uraon)
HAHA!
Tim David is proving why MI was not trusting him after buying him for 8 cr 😂 that was really easy catch at that level of playing !!
— Techwarmth (@techwarmth)
LOL!
8 cr for Tim david! Join sharne warne asap. Sams u too
— MS (@XaviBaIl)
BAN!
Tim David should be banned from Cricket immediately and those MI fans who wanted him in the team should be removed from twitter as a safety precaution bhaiya I m rit??
— 𝑨𝒌𝒖𝒍 𝑻𝒉𝒂𝒌𝒖𝒓 ( SRT FOR LIFE) (@Loyalsachfan01)
Comments
Leave a comment0 Comments