RCB crush Delhi Capitals by 9 wickets

Royal Challengers Bengaluru hammered Delhi Capitals by 9 wickets with 81 balls remaining in Match 39 of the Indian Premier League, with Josh Hazlewood producing a devastating spell of 4 for 12 in 3.3 overs. RCB bowled DC out for just 75 in 16.3 overs before racing to 77 for 1 in only 6.3 overs to seal one of the most emphatic wins of the season.

This was a result that further strengthened RCB’s push in the league stage rather than deciding any head-to-head contest, and it followed a run of strong results for Bengaluru across the tournament. They had already won Matches 1, 11, 20, 23 and 34 before adding Match 39 here, while Delhi were left to absorb a heavy defeat after earlier wins in Matches 5, 8 and 26. With Match 39 now complete in the 70-match league phase, the tournament rolls on with Punjab Kings vs Rajasthan Royals scheduled for Tuesday, April 28.

RCB’s bowlers blow DC away

Delhi’s innings never settled. Sahil Parakh fell for 0 from 2 balls, KL Rahul managed just 1 from 3, Nitish Rana scratched to 1 from 9, and Sameer Rizvi was dismissed for 0 off the first ball he faced. By the time Axar Patel went for 0 from 3 balls, RCB had ripped through the top order and the Capitals were deep in trouble.

Hazlewood was the standout act, claiming 4 for 12 from 3.3 overs and repeatedly hitting a testing length. Bhuvneshwar Kumar was just as incisive at the top, taking 3 for 5 in 3 overs and giving away almost nothing. Suyash Sharma’s 1 for 7 from 4 overs tightened the squeeze through the middle overs, while Krunal Pandya returned 1 for 9 in 2 overs.

Only Abishek Porel and David Miller gave Delhi anything close to resistance. Porel top-scored with 30 from 33 balls, striking three fours, while Miller made 19 from 18 with three fours. Their effort at least dragged DC beyond complete humiliation, and Kyle Jamieson chipped in with 12 from 13, including a four and a six. But the lack of partnerships defined the innings, and 75 was never likely to be enough on a night when RCB’s attack was relentless.

Fast finish in the chase

RCB made light work of the target. Jacob Bethell came out hard for 20 from 11 balls, with one four and two sixes, setting the tone immediately. Even when Kyle Jamieson removed him and finished with 1 for 42 in 3 overs, the chase was already firmly under control.

Virat Kohli continued his excellent tournament form with 23 from 15 balls, including a four and two sixes, before Devdutt Padikkal finished the match in explosive style. Padikkal blasted 34 not out from just 13 balls at a strike rate of 261.5, hammering three fours and three sixes as RCB surged to 77 for 1 in only 6.3 overs.

Delhi’s bowlers had no answer. Dushmantha Chameera went for 18 in 2 overs, Axar Patel conceded 5 in his single over, and T Natarajan’s three balls cost 12 runs as the finish came in a flash.

Key performers

Josh Hazlewood: 4/12 in 3.3 overs, Player of the Match
Bhuvneshwar Kumar: 3/5 in 3 overs
Abishek Porel: 30 off 33 balls
Devdutt Padikkal: 34* off 13 balls
Virat Kohli: 23 off 15 balls

NerdSports Stat: Delhi Capitals’ top six batters combined for just 7 runs, while RCB chased the entire target in 39 balls with 81 deliveries still unused.

Pre-match win probability had RCB at 58.21% to Delhi’s 41.79%, but even that edge did not hint at a demolition this complete. Bengaluru’s established tournament strengths were visible again: Bhuvneshwar Kumar, who came into the match with 15 wickets in 10 matches, struck early, and Kohli, who had already amassed 437 runs in 10 matches, helped ensure there was no stutter in the chase.

For Delhi, the defeat was especially jarring given KL Rahul had entered the match as their leading run-scorer with 515 runs in 10 matches, while Sameer Rizvi had 306 runs at a strike rate of 153.8. Neither could influence the contest, and once the early wickets fell, the innings never recovered.

RCB now move on to face Gujarat Titans on Thursday, April 30, while Delhi Capitals’ next fixture is against Rajasthan Royals on Friday, May 1. In a long IPL league season there is always another match around the corner, but this was the sort of dominant performance that can shape momentum and net run rate in equal measure.

Frequently Asked Questions