hi INDiA
South Asian Views On Global News - Update 24X7

‘Lazy Batting’: Delhi Capitals Fans Blame Shikhar Dhawan’s Slow Innings For Crucial Loss


For the third year in a row, Delhi Capitals were in the top-three during the regular season but got knocked out in the playoffs of the Indian Premier League. However, this time around, the angry fans are blaming their opener, Shikhar Dhawan, for being the one who started off extremely slow and didn’t help his side get enough runs to protect in the second half of the match.

View this post on Instagram

Opening the batting with Prithvi Shaw, the 35-year old southpaw batter took 39 deliveries to put up 36 runs on the board. During his time on the pitch, he hit just one 4 and two 6’s.

His opening partner, Shaw had a rather stormy start in the power play and struck two 4’s and one 6 in the first 11 balls that he had faced. After scoring 18 runs, he lost his wicket to an LBW appeal by Varun Chakravarthy.


Varun Chakravarthy does the job for #KKR as he traps Prithvi Shaw in front for 18.

IPL#IPL2021 #KKRvDC pic.twitter.com/2avQKsxiDh

— Sportskeeda India (@Sportskeeda) October 13, 2021

Then came Marcus Stoinis at the number three spot and this is potentially where the match slipped out of the hands of Rishabh Pant’s side. When Shaw lost his wicket, the DC scoreboard read 32/1 in 4.1 overs. By the time Stoinis got out, Dhawan and he had managed to put up just 39 runs in 44 deliveries.

Things got even worse by the time Dhawan lost his wicket as at that point, DC were at 83/3 in 14.1 overs and in big trouble too.

Sikhar dhawan played very slow
If sikhar add just 10 run more so delhi will win this match

— Cp purohit (@chandusevak10) October 14, 2021

Sending Stoinis at no.3 and Dhawan slow batting cost Delhi capitals show much ! #DelhiCapitals#KKRvDC

— Rajat Bajpai (@Rajatbajpai6) October 13, 2021

hi INDiA News On The Go...

Dhawan and Stoinis slow strike rate costed match for delhi , Hard luck @DelhiCapitals . #KKRvDC #IPL2021

— Anuj (@Anuj40574036) October 13, 2021

Still 135 is never going to win you matches. Trio Of Dhawan, Stoinis and Iyer played too slow in middle. All they needed was to bat with SR of 100-110 and they would have easily crossed 150. Then the terrible run out of hetmyer too costed 5-10 runs. Overall they panicked.

— #WEWANTXAVI (@ShashankSatyam0) October 13, 2021

Yup ..kya kar sakte ..
Runs hi nai banaoge toh defend kya karoge ..
Slow players in team ..dhawan n iyer

— kawaljeet singh Bacher (@VickySi75961809) October 13, 2021

Shikhar Dhawan slow innings troubled delhi..
What is your opinion?

Don’t blame spin bowling ..

Akshar and Ashwin are far better with varun and narraine . @DeepDasgupta7 @IrfanPathan @ESPNStatsInfo #UnacademyAskTheExperts

— Ashish Shivhare (@Ashishshiv096) October 13, 2021

However, to be fair to the leading batter, the Sharjah pitch, which is commonly known to be a batting-friendly space, was completely unpredictable. There was uneven bounce and the turn on some of the deliveries made it borderline impossible to gauge the direction in which the ball would go after the bounce.

Additionally, Dhawan has been one of the most consistent batters in the entire league this season. In the 16 matches that he had played, he scored 587 runs with a strike rate of 124.62 and was the third leading run-scorer in the race for the orange cap.

View this post on Instagram

Unfortunately, by the time it was Kolkata Knight Riders’ turn to bat, the Sharjah pitch had retained much of its batting-friendly characteristics, and their opener, Venkatesh Iyer made the most of it, scoring a mighty 55 off 41 deliveries. However, Iyer’s partner Shubman Gill played a relatively slow innings and scored 46 runs in as many balls.

Having said that, one has to give credit to the exceptional bowling attack that the Delhi team has. Not only were they able to stretch the match till the very last over, but they were also within winning distance if they’d had just a few more runs to defend.

English English Gujarati Gujarati Hindi Hindi
gtag('set', {'user_id': 'USER_ID'}); // Set the user ID using signed-in user_id.