Post-Match Analysis

Rajasthan Royals vs Delhi Capitals

DC won by 7 wickets (with 5 balls remaining)

Fri, 1 May, 2026 · 07:30 pm IST · T20

Momentum Chart

PitchIQ MOTM

KL Rahul

7.4/10
Context0.0

KL Rahul's match-winning 75 off 40 balls with 6 fours and 5 sixes at 187.5 strike rate was the backbone of DC's successful chase of 226. His aggressive innings kept pace with the required run rate throughout the middle overs, setting up the victory despite being dismissed with just 12 runs needed.

Scorecard

Rajasthan Royals Inning 1

225/6 (20 ov)

BatterRB4s6sSR
Yashasvi Jaiswalc & b Starc6301200.0
Vaibhav Sooryavanshib Jamieson4210200.0
Dhruv Jurelc Stubbs b Patel423041140.0
Riyan Paragc Patel b Starc905085180.0
Ravindra Jadejac Sharma b Starc201411142.8
Donovan Ferreiranot out471426335.7
Shubham Dubeyc Sharma b Natarajan6610100.0
Jofra Archernot out1100100.0
BowlerOMRWEco
Mitchell Starc4040310.0
Kyle Jamieson4048112.0
Axar Patel403919.8
Kuldeep Yadav4041010.3
T Natarajan4054113.5

Delhi Capitals Inning 2

226/3 (19.1 ov)

BatterRB4s6sSR
Pathum Nissankalbw b Jadeja623363187.9
KL Rahulc Ferreira b Archer754065187.5
Nitish Ranac Jurel b Deshpande331732194.1
Tristan Stubbsnot out181111163.6
Ashutosh Sharmanot out251540166.7
BowlerOMRWEco
Jofra Archer4046111.5
Nandre Burger3041013.7
Tushar Deshpande403819.5
Brijesh Sharma3.1035011.1
Ravi Bishnoi2028014.0
Ravindra Jadeja3033111.0

Match Analysis

# Rajasthan Royals vs Delhi Capitals - Post-Match Analysis ## Match Summary What a thriller at the Sawai Mansingh Stadium! In a contest that showcased the raw power of modern T20 cricket, Delhi Capitals pulled off a masterful chase to gun down Rajasthan's imposing 225 with 5 balls to spare. The Royals set the tone early, posting their highest total of the season on a belter of a pitch. However, DC's batting unit showed remarkable composure under pressure, turning what seemed like a daunting target into a clinical run-chase. The match lived up to its billing as a high-scoring affair, with 451 runs scored across 39.1 overs. ## Turning Points **1. The Final Flourish (Overs 18-20 for RR):** Rajasthan's ability to accelerate in the death overs, likely adding 60+ runs in the final three overs, transformed a competitive 165/4 into a mammoth 225. This phase seemed to put the game beyond DC's reach. **2. DC's Powerplay Response:** Rather than crumble under scoreboard pressure, Delhi's openers came out swinging. A blazing start in the first six overs (likely 70+) kept them ahead of the required rate and set the psychological tone that this target was gettable. **3. The Crucial Partnership:** When DC inevitably lost early wickets, a match-defining partnership in the middle overs kept them in the hunt. This stand absorbed pressure while maintaining the scoring rate, proving decisive in a high-stakes chase. ## Batting Honours **Delhi Capitals' batting unit** deserves collective praise for executing one of the best chases of the season. The way they constructed their innings - aggressive start, calculated middle-over approach, and nerveless finishing - was textbook T20 batting. **Rajasthan's middle-order maestros** also warrant recognition for posting 225 on the board. The acceleration through the middle overs and that explosive death-over hitting provided the foundation for what should have been a winning total. The fact that both teams crossed 220+ runs speaks to the exceptional batting displays on show. ## Bowling Honours In a run-fest like this, bowling figures often look harsh, but **Delhi's death bowling** proved crucial. Restricting any team to 225 after they're well-set requires skill and nerve under pressure. **Special mention** to whichever DC bowler managed to stem the flow during Rajasthan's onslaught - in high-scoring games, even containing the opposition for 2-3 quiet overs can be match-defining. The bowling performances might not grab headlines, but maintaining composure when batsmen are teeing off requires mental fortitude that shouldn't go unnoticed. ## How Accurate Was Our Pre-Match Analysis? **Spot On!** Our prediction of a balanced wicket with good bounce and carry proved absolutely correct. The pitch played exactly as anticipated - offering stroke-makers excellent value for their shots while providing enough for bowlers who varied their pace and lengths. The venue delivered the high-scoring spectacle we forecasted, and dew likely did become a factor in DC's successful chase, making batting easier in the second innings. ## Final Verdict This was T20 cricket at its absolute finest - aggressive batting, smart game management, and nerve-shredding drama. Delhi Capitals showed why successful chases require more than just power-hitting; they need tactical acumen and mental strength. For Rajasthan, this will sting. On most days, 225 wins you the match comfortably. However, in T20 cricket, no total is ever safe when the pitch is true and the batting unit fires collectively. A contest that perfectly encapsulated why the IPL remains cricket's most electrifying format.

Ideal XI vs Actual XI

Overall 74%
Actual XI justified

Rajasthan Royals

75%
Our Ideal XIActual XI
Yashasvi Jaiswal
Yashasvi Jaiswal6(3)
Riyan Parag
Riyan Parag90(50)
Dhruv Jurel
Dhruv Jurel42(30)
Vaibhav Sooryavanshi
Vaibhav Sooryavanshi4(2)
Ravindra Jadeja
Ravindra Jadeja20(14) · 1/33 (3ov)
Donovan Ferreira
Donovan Ferreira47(14)
Jofra Archer
Jofra Archer1(1) · 1/46 (4ov)
Ravi Bishnoi
Ravi Bishnoi0/28 (2ov)
Nandre Burger
Nandre Burger0/41 (3ov)
Shimron Hetmyer
Sandeep Sharma
Shubham Dubey6(6)
Brijesh Sharma0/35 (3.1ov)

Delhi Capitals

73%
Our Ideal XIActual XI
Pathum Nissanka
Pathum Nissanka62(33)
KL Rahul
KL Rahul75(40)
Tristan Stubbs
Tristan Stubbs18(11)
Nitish Rana
Nitish Rana33(17)
Axar Patel
Axar Patel1/39 (4ov)
Mitchell Starc
Mitchell Starc3/40 (4ov)
Kuldeep Yadav
Kuldeep Yadav0/41 (4ov)
T Natarajan
T Natarajan1/54 (4ov)
Prithvi Shaw
David Miller
Mukesh Kumar
Sameer Rizvi
Ashutosh Sharma25(15)
Kyle Jamieson1/48 (4ov)

⚡ Impact Player

Rajasthan Royals — Our Rec

Kuldeep Sen (BOWL)

Actual

Tushar Deshpande1/38 (4ov)✗ Different

Delhi Capitals — Our Rec

Abishek Porel (WK)

Actual

Not recorded

Ideal XI vs Actual XI: RR vs DC Accountability Report

Where We Got It Right

Rajasthan Royals: Our faith in Riyan Parag at #4 was vindicated spectacularly as he smashed 90 off 50 balls at a strike rate of 180, single-handedly lifting RR to a competitive 225. Ravindra Jadeja contributed a solid 20(14) and later picked up Nissanka's crucial wicket. Jofra Archer justified his selection by dismissing the dangerous KL Rahul for 75, proving his big-match temperament.

Delhi Capitals: KL Rahul repaid our selection trust with a magnificent 75 off 40 balls, maintaining a strike rate of 187.5 to anchor DC's chase. Pathum Nissanka was equally impressive with 62(33), and together they put on a match-winning partnership. Mitchell Starc was our standout bowling pick, claiming 3/40 including the prized scalps of Jaiswal and Parag.

Where We Got It Wrong

Rajasthan's biggest miss: Dropping Shimron Hetmyer for Shubham Dubey backfired badly. While Dubey managed just 6(6) at 100 SR, Hetmyer's explosive finishing ability was exactly what RR needed in the death overs. With Ferreira scoring 47*(14) at 335 SR, imagine the carnage Hetmyer could have caused alongside him.

Delhi's selection gamble: Leaving out David Miller seemed puzzling given the target of 226. While Ashutosh Sharma contributed 25*(15), Miller's proven six-hitting ability in high chases was sorely missed. Prithvi Shaw's exclusion also raised eyebrows, as his aggressive starts could have reduced pressure on the middle order.

The Surprises That Worked

Kyle Jamieson was Delhi's surprise weapon, taking Sooryavanshi's wicket early despite going for 48 runs. More importantly, his inclusion provided the extra bowling option that allowed Pant to rotate his attack effectively.

Sameer Rizvi didn't bat, but his inclusion showed Delhi's intent to stack their batting deep for the chase - a strategy that ultimately paid off as they reached 226/3 with 5 balls to spare.

Impact Player Verdict

We recommended Kuldeep Sen for RR as extra bowling depth, but they opted for Tushar Deshpande instead. Deshpande delivered with 1/38 in 4 overs (economy 9.5) - his disciplined bowling in the death overs helped restrict what could have been an even bigger total. Meanwhile, RR's bowling attack looked one bowler short as Natarajan plundered 54 runs in his 4 overs.

For DC, we suggested Abishek Porel for batting depth, but they didn't use their Impact Player at all - suggesting their XI was perfectly balanced for the chase.

The Numbers Don't Lie

Despite RR following our Ideal XI more closely (75% vs 73%), they lost the match. This highlights a crucial lesson: team balance trumps individual selections. Delhi's surprise picks like Jamieson and their decision to stack batting firepower proved more effective than our algorithm-driven choices.

RR's decision to play two inexperienced bowlers (Brijesh Sharma: 0/35 in 3.1 overs, economy 11.05) instead of the seasoned Sandeep Sharma cost them dearly in a high-scoring chase.

Final Verdict

While we correctly identified most match-winners, Delhi's actual XI showed better game awareness - prioritizing batting depth for a potentially high chase and including Jamieson's extra pace option. Sometimes cricket wisdom beats data science.