Ind vs WI 2022 | Twitter reacts as KL Rahul gets run-out after mixup with Suryakumar Yadav
Indian batsman KL Rahul was run out in the second ODI against the West Indies at the Narendra Modi Stadium in Ahmedabad after a mix-up with Suryakumar Yadav. KL Rahul missed the first game but made his return to the side in second fixture and batted at number 4 against West Indies.
KL Rahul was batting fluently until a mixup with Suryakumar Yadav resulted in him being run out in the second ODI against West Indies at the Narendra Modi Stadium in Ahmedabad. Rahul had hit the ball to the left of deep cover and was looking for the second run. Suryakumar Yadav responded for the run as KL Rahul was running towards the danger end. However, during the run KL Rahul just stopped for a second which resulted in his run out.
KL Rahul scored 49 off 48 balls on his return to the side in place of Ishan Kishan after missing the first ODI against West Indies. The right-handed batsman batted at number 4 on Wednesday, a spot which Rishabh Pant was batting regularly at during the South Africa series.
During his innings, KL Rahul struck four boundaries and two sixes.
Here is how Twitter reacted to his KL Rahul's runout.
RAHUL GONE!
— jennifer (@jennife74834570) February 9, 2022
BIG FISH!
It was KL Rahul’s own call.💔💔💔 Misjudgement, and he’s missed out on a big one perhaps. #INDvsWI
— Sombir Singh jat (@SombirSinghjat1) February 9, 2022
UNFAIR?
Why does something go unfair during match-time! KL Rahul is gone for 49 as soon as I tweeted. But he’s played a very fine innings, 49 from 48 👏 #INDvWI
— Mandar Tikam (@MandarTikam) February 9, 2022
HAHA!
#INDvWI #INDvsWI
— Hemant (@Sportscasmm) February 9, 2022
KL Rahul: "Overthinker hu bhai, isliye beech mai sochne ke liye Ruk gaya tha" pic.twitter.com/biWvqbM2Ir
BRAINFADE!
#INDvWI brainfade from the vice- captain🤯🤯#rahul #klrahul Not for the first time 🤦🏻♂️🤦🏻♂️
— ಶೂನ್ಯ 😴🥱 (@Vasisth85582631) February 9, 2022
RAHUL'S FAULT?
Kl Rahul Fault 😡😡😡😡😡😡
— Daksh Saini (@ImSaini45) February 9, 2022
Comments
Leave a comment0 Comments