IPL 2023, KKR vs GT | Twitter bashes Rahmanullah Gurbaz for letting KKR batters burn DRS from non-strikers' end
Similar to many sports, cricket is a team game that requires support from different individuals. But teams face troubles when things go south, and Rahmanullah Gurbaz, despite going berserk with the bat, was the one for KKR on Saturday as he allowed two plumb LBWs to challenge to receive criticism.
Coming in place of injured Jason Roy, Kolkata Knight Riders’ wicket-keeper batter Rahmanullah Gurbaz made an instant impact against Gujarat Titans at Eden Gardens. Walking to bat as an opener in Match 39 of IPL 2023, the Afghanistani raced to 67 runs off just 33 balls, which included six sixes and four fours, and did not stop yet. However, people were mad at him in between, and their sentiments had nothing to do with his batting.
To begin with, N Jagadeesan, batting on 19 off 14 balls, was trapped leg before by a length delivery by Mohammed Shami during the third ball. The umpire raised his finger immediately after the Titans’ appeal, but Jagadeesan had doubts about his decision. He went on to have a chat with Gurbaz, who suggested that he should go for a DRS. The replay, as expected, showed the ball would hit the middle of the middle stump, and that’s why the Tamil Nadu batter had to walk back to the pavilion.
Almost the same thing happened during the 11th over, and only the individuals were changed. This time, the batter was Venkatesh Iyer, and the bowler who pinned him leg before was Noor Ahmed. Despite it looked very straightforward dismissal to the naked eye, Iyer went to discuss with Gurbaz regarding the matter, and again, the Afghan could not give him the right suggestion. The replay again showed the LBW was plumb, as the ball would the middle of the middle stump for the second time in the innings, leading the netizens to go furious.
Total waste!
— NANA PII (@NANAPII2320) April 29, 2023
Have a look at this as well!
Horrific review
What a horrific review by V Iyer... he brings down the scoring rate wastes an extremely precious review no faith in his batting skills nowadays...his career started well but since ???Team must have some protocol in place to take a Review specially the second one!!!#KKRvsGT
— Lokesh Shankarappa (@lokyshanks) April 29, 2023
Plumb!
2 very poor reviews by KKR. Both venky Iyer and jagdeeshan are looking plumb our. Non strikers should ask batter to not review if it's looking plumb. Bcz Almost all batters review for lbw decision irrespective of hoe plumb it was. Thoughts @gurkiratsgill @CricCrazyJohns
— Samkit Hitman (@SamkitM15207196) April 29, 2023
Not sure at all
Venkatesh Iyer best utilised at the top. Not sure this No. 3-4 role suits. If Gurbaz is fit and available, their wicketkeeping problem is solved too. Them wanting to give opportunities to Jagadeesan on the back of his domestic form is understandable, but it hasn't worked so far.
— Shashank Kishore (@captainshanky) April 29, 2023
Pathetic!
Jagadeesan first and now Venkatesh Iyer. DRS taken on two of the most plumb LBW decisions, simply pathetic. KKR have now lost both of their reviews. pic.twitter.com/ynKyNHvMsO
— Rahul Sharma (@CricFnatic) April 29, 2023
Horrible shot!
Mr Iyer ( @venkateshiyer)....you wont see kids attempting such horrible shot!!🤦♂️@KKRiders https://t.co/CB2FxAVE0F
— #Nitin Kumar Upadhyay🇮🇳 (@NitinKumar7728) April 29, 2023
What is that?
Venky Iyer aur Nitish ko line and length per ball daalo
— dilseᴷⁿⁱᵍʰᵗᴿⁱᵈᵉʳ (@iemSRKian) April 29, 2023
BC Woh log khud wicket denge
Reverse sweep
Scoop
Paddle sweep Karke#kkr
Dance it
Kathakali from Iyer...Venkatesh Iyer 😋#IPL2023 | #KKRvGT pic.twitter.com/9l6B9S6tIk
— 🏏Flashscore Cricket Commentators (@FlashCric) April 29, 2023
Killed momentum
Venkatesh Iyer killed the momentum of the game. #KKRvsGT #TATAIPL2023 #Crickettwitter
— SECOND SLIP (@MerchantCricket) April 29, 2023
Lite version
Venkatesh Iyer is just a sasta version of KL Rahul, statpads in every match
— Debarghya C (@DebarghyaChak17) April 29, 2023
Comments
Sign up or log in to your account to leave comments and reactions
0 Comments