Captaincy Blunder And? Mistakes In RCB Match That DC Should Not Repeat vs KKR

Jatin

DC will be up against KKR [Source: @iplt20.com]DC will be up against KKR [Source: @iplt20.com]

It’s crunch time in the IPL and Delhi Capitals know they can’t afford to slip up now. Placed at fourth spot in the IPL 2025 points table with six wins in nine games, DC have done a lot right this season but their last outing against RCB was a reality check.

They had the match in their grip, but let it slip through their fingers like sand. Now, up against Kolkata Knight Riders at the Arun Jaitley Stadium on Tuesday, DC need to bring their A-game and there is no room for deja vu.

Here are 3 mistakes from the RCB clash that Delhi Capitals must absolutely steer clear of if they want to stay in the playoff zone.

1. Middle Overs Tempo Was Missing in Action

Delhi Capitals started decently against RCB but lost the plot in the middle overs.

Both Faf du Plessis and KL Rahul had their eye in but couldn't up the ante when it mattered. They got stuck rotating the strike without finding the fence regularly. And the worst part? Just when they needed to shift gears, they lost their wickets.

Faf’s 22 off 26 and Rahul’s 41 off 39 were the classic case of getting a start but failing to cash in. In T20 cricket, especially against teams like RCB, a slow crawl in the middle overs is like handing over momentum on a silver platter.

Against KKR, DC can’t afford to let the game drift. With Sunil Narine, Varun Chakravarthy, Andre Russell breathing fire, they will need to keep their foot firmly on the accelerator.

2. Captaincy Blunders

This was the real sliding doors moment for DC against RCB. With just 17 runs needed off 12 balls, it was the perfect moment for Axar Patel to throw the ball to his match-winner, Mitchell Starc.

Starc has already shown this season he can snatch wins from the jaws of defeat and pressure bowling is his bread and butter. Instead, Axar went for Mukesh Kumar, who had already leaked runs and was low on confidence.

The result? Mukesh conceded the runs needed in just three balls, game over, no contest. Had Starc bowled that penultimate over, the game could’ve gone right down to the wire, and pressure might’ve tilted the balance DC’s way.

Against KKR, Axar needs to be sharper with his bowling calls, especially at crunch moments. Big players are there for big moments and you don’t save your missiles when you’re under attack.

3. Axar Patel’s Over-Usage

Another subtle but crucial mistake: Axar Patel bowled out his three overs upfront. Sure, Axar was brilliant with the new ball, finishing with 2/19 from 4 overs, tight, tidy and effective. But with him bowling three overs by the 5th over, DC had no bankable spinner to control the middle overs.

Kuldeep Yadav tried his best but went wicket-less while Vipraj Nigam bowled just one over for 12 runs, and suddenly, the pressure valve was gone. RCB’s batters, especially Krunal Pandya, found easy pickings without worrying about squeezing overs from both ends.

Axar is not just a wicket-taker; he is a run-choker. DC missed a trick by not keeping his overs handy in the middle overs. In T20s, especially against an aggressive side like KKR, you need your smartest bowler to be in the game when it’s in the balance.