The fielding debacle began in the ninth over bowled by Kuldeep Yadav, with Axar Patel and Shai Hope missing straightforward catches, visibly frustrating the Indian spinner. The troubles continued as Tristan Stubbs failed to hold onto a simple chance in the 10th over when Will Jacks mistimed a shot towards extra cover. To compound matters, Delhi's stand-in skipper dropped another catch, giving Patidar yet another lifeline at cover. In totality, the home side missed four easy catches within the gap of three overs.
As the flurry of poor fielding unfolded, the Twitterverse was left in shock by the Capitals' uncharacteristic display.
What's going on?
— AK DS (@AKDS580838)
Too many
So many catch drops by DC players today and intentionally they are leaving boundaries, RCB owner match fixing time to ban this RCB 🤬👊🏻
— 𒆜Harry Billa𒆜 (@Billa2Harry)
Finally
Finally Axar takes the catch
— Cheers To The Underdogs🍻🇿🇼 (@nyamutsita)
Hypocrite
Hai bhai ,abb koye fixing nahi bole ga RCB ka fan ,,,,🤡..
— MR.(⚡) (@Indiancricket99)
4 catch drop..!!!
Hypocrite rcb fans 🤡
Fixed?
— g0v!ñD $#@®mA (@rishu_1809)
I think it's RCB whose matches are getting . So many Catch dropped by PBKS that day, helped RCB to put a High Total. And Delhi Capitals are repeating the same script.
On fire
Back to back Half centuries..💯💥
— Vishwanath! (@AvishTweetss)
Prince Rajat Patidar..🔥✨
Well played
Rajat Patidar 50* (29) 🔥
— Prasad K (@Prasad_K2000)
Well played Rajat 👏
Now convert this fifty into a big score.
Again
3 catch drop 😲
— Nithin Gm (@Nithin_gm1)
Once again
Rajat Patidar Once Again Fire🔥💥
— Ashok Patidar (@ashokpatidar190)
Pure diamond
RAJAT means Silver But He is pure Diamond.Well played Mr consistent Rajat Patidar.
— Sunny Pandey (@sunnypandey92)
Comments
Leave a comment0 Comments