IPL 2024, RR vs DC - 3 Things That Went Wrong For DC

Delhi Capitals faced their second consecutive loss in IPL 2024 (IPLT20.com)Delhi Capitals faced their second consecutive loss in IPL 2024 (IPLT20.com)

Delhi Capitals witnessed their ambitions get blown off course for the second time in a row in IPL 2024, succumbing to a 12-run defeat at the hands of the Rajasthan Royals at the Sawai Mansingh Stadium in Jaipur on Thursday.

Having been invited to bat first, the Royals’ innings seemed to falter, finding themselves in a dismal position at 36/3 after 7.2 overs.

However, the innings turned dramatically as Riyan Parag took the helm, steering the ship with an extraordinary unbeaten 84 from 45 balls. Parag's innings, filled with seven boundaries and six maximums, saw him cruising at a strike rate of 186.67, catapulting Rajasthan to a formidable 185/5.

The Capitals, on their part, kicked off their chase with vim and vigour, but the dismissal of their opening duo, David Warner and Mitchell Marsh, marked the beginning of their unravelling.

Tristan Stubbs put up a valiant fight, blasting a quickfire 43 off 23 balls, but found himself a lone warrior as support from the other end fizzled out. Despite his efforts, DC closed at 173/5, unable to bridge the gap.

There were several factors that led to Delhi’s undoing. Here are three things that went wrong for DC vs RR in their second game of IPL 2024.

1. Squandering a Stellar Start

Kuldeep Yadav dismissed danger man Jos Buttler for 11 (IPLT20.com)Kuldeep Yadav dismissed danger man Jos Buttler for 11 (IPLT20.com)

Delhi Capitals began with a flourish, swiftly dismantling the top order of the Rajasthan Royals' batting lineup, reducing them to an abysmal 36/3 within the first 7.2 overs. This early dominance, however, gradually fizzled out as the Capitals' bowlers veered off course, losing the plot and their earlier discipline.

The partnership between Riyan Parag and Ravichandran Ashwin proved to be a linchpin for the Royals, meticulously crafting a crucial 54-run stand off just 35 balls, thereby snatching the momentum back into their court.

This lapse in the middle overs by the Capitals, characterized by a lack of wicket-taking and loose bowling, allowed the Royals to stage a remarkable recovery and eventually post a competitive total of 185—a score that could have been significantly lower had Delhi maintained their stranglehold.


2. Nortje's Nightmare Over

Riyan Parag took Anrich Nortje to the cleaners (IPLT20.com)Riyan Parag took Anrich Nortje to the cleaners (IPLT20.com)

Anrich Nortje's final over spelled disaster for Delhi Capitals, as Riyan Parag unleashed a barrage of boundaries, turning what could have been a moderate total into a massive target.

This 25-run over transformed the complexion of the game, propelling the Royals from a manageable 160 to an above par 185.

The costly over by Nortje dramatically tilt the scales, ultimately becoming the nail in the coffin for the Capitals, who fell short by 12 runs in their chase.

3. Lost Momentum After Powerplay

Delhi Capitals failed to capitalize on the great start (IPLT20.com)Delhi Capitals failed to capitalize on the great start (IPLT20.com)

The initial burst in the powerplay, where the Capitals notched up 59/2, laid a robust foundation for what appeared to be a manageable chase.

However, the plot took an unexpected turn as key batsmen David Warner and Rishabh Pant prematurely exited the stage.

Warner's dismissal, particularly after settling in, along with Pant's laborious 28 off 26 balls, piled on the pressure, effectively stalling the momentum.

Despite Tristan Stubbs' gallant 23-ball 44, the absence of a supporting cast meant that the early advantage gleaned from the powerplay gradually dissipated into thin air.

This unravelling showed the critical importance of sustaining the momentum and capitalizing on it, a lesson the Capitals would rue as they fell agonizingly short of their target.