DC vs RR Match 62 Recap: Kotla Nightcap Breakdown


Share this article
DC vs RR at the Arun Jaitley Stadium was the kind of nightcap that rewards patience. Both teams lost 3 wickets inside the powerplay, both leaned on a middle-overs anchor, and both found themselves needing 11 runs an over at the death. RR got there with 4 balls to spare, and the difference was a 14th-over bowling switch that DC didn't make.
Scorecard at a glance
- Delhi Capitals: 158/7 in 20 overs (Tristan Stubbs 49, Faf du Plessis 38, Axar 26; Sandeep Sharma 2/24, Ashwin 2/28)
- Rajasthan Royals: 159/4 in 19.2 overs (Riyan Parag 58*, Jurel 41, Hetmyer 28; Kuldeep Yadav 2/26, Mukesh Kumar 1/30)
- Result: Rajasthan Royals won by 6 wickets
A 6-wicket win with 4 balls to spare is the kind of margin that makes the chase look easier than it was. RR were 41/3 inside the 7th over; the rebuild from there is the story. The standings shift is on the IPL 2026 points table.
Top-order failure tax
| Team | Powerplay score | Wickets lost | Cost |
|---|---|---|---|
| DC | 38/3 | 3 | -22 vs season avg |
| RR | 41/3 | 3 | -18 vs season avg |
Both teams paid the powerplay price. DC lost Fraser-McGurk, Karun Nair and Faf du Plessis inside 6 overs. RR lost Jaiswal, Tom Banton and Hetmyer inside 6 overs. (Hetmyer's 28 was in his rebuild knock at 5.)
Innings 1: Stubbs anchors a wreck
Tristan Stubbs played the season's most underrated knock at 49 off 38. He came in at 22/2 in the 4th over, took 14 balls to settle, and constructed an innings around hitting one boundary an over without taking the slog risks. Faf du Plessis's 38 off 28 was the assist, but he fell in the 14th to a slower ball.
The death overs were tepid. Axar Patel made 26 off 17 (his first sub-50 strike-rate finish of 2026), and DC got from 124/4 to 158/7. The 19th over (Sandeep Sharma) was the choke: 4 runs and 2 wickets.
Innings 2: Parag's nightcap
Riyan Parag came in at 41/3 in the 7th over with the chase looking dead. He took 12 balls to reach 10, then got himself in. Dhruv Jurel's 41 off 32 was the second-engine knock, but it was Parag's 58 not out off 39 that closed it.
The decisive moment: Axar didn't bring Kuldeep Yadav back for the 14th over. Kuldeep had bowled 2 overs by then (4 wickets total in his last two outings), and DC's middle-overs plan was leaning on Mukesh Kumar. Mukesh went for 12 in the 14th. From a chase that needed 11 RPO, RR were back to a chaseable 8.
Top 3 turning points
- Parag arriving at 41/3 (innings 2): The rebuild started here. Win-prob delta: 0% (this is a base state, not a turning point in the strict sense).
- Axar's decision to bowl Mukesh in the 14th instead of Kuldeep (innings 2): Cost DC 12 runs and the chase. Win-prob delta: +14% RR.
- Sandeep Sharma's 19th over for 4 with 2 wickets (innings 1): Capped DC at 158. Win-prob delta: +11% RR.
Captain grades
Riyan Parag (c) (RR) โ A-: Read the chase correctly, took the Parag rebuild brief on himself rather than trying to slog out of it, and the bowling rotation in innings 1 (Sandeep at the death) was sharp. Lost half a grade for the powerplay collapse.
Axar Patel (c) (DC) โ C+: Holding back Kuldeep was the night's mistake. His own 26 off 17 was a useful death cameo but the bowling rotation in the chase was too cautious. With 158 to defend, you go all-in with your best wicket-taker; he didn't.
Top-order failure tax: a season trend for DC
This is the third match this season where DC's top three have been gone inside the 7th over. Without Stubbs they would have been 105 all out. The structural fix is to send Axar up the order to 3 (he's done it for India) or to bring in a steady opener. The current Fraser-McGurk-Karun Nair powerplay attempts are too risky.
Middle-overs bowling switch
The single most-discussed call from this match. Axar's reasoning was likely to save Kuldeep's 4th over for Parag at the death. That's defensible logic. The miss: Parag was the threat in the middle overs already, and Kuldeep's wicket-taking impact at that stage was higher than at the death.
Dream11 retro grade
| Player | Role | Points | Verdict |
|---|---|---|---|
| Riyan Parag | Captain | 132 | Elite |
| Jurel | VC | 84 | Strong |
| Stubbs | Top order diff | 88 | Strong |
| Kuldeep | Bowler | 56 | Solid |
| Sandeep Sharma | Bowler diff | 64 | Sneaky good |
Captain Parag was the runaway pick. Track on the cap-race predictor. Full Dream11 hub at /dream11.
Playoff and NRR implications
RR move to 14 points and stay third; their NRR climbs from +0.27 to +0.32. DC slip to seventh on 11 with NRR dropping to -0.05. Their playoff math now requires 3 wins from 3 plus help from other teams. See the NRR table breakdown.
What this means going forward
RR have figured out how to win without their best balls. The Parag-Jurel-Hetmyer middle order is the league's most dependable. DC have to fix the powerplay or accept that Stubbs will play 50% of their innings. Axar's captaincy is steady with the ball in hand, less reliable in real-time bowling-rotation decisions.
FAQ
Q: Who won DC vs RR Match 62? A: Rajasthan Royals won by 6 wickets, chasing 159 with 4 balls to spare.
Q: Who was Player of the Match? A: Riyan Parag for his unbeaten 58 off 39 balls.
Q: What was the captaincy mistake for DC? A: Axar held back Kuldeep Yadav from the 14th over and let Mukesh Kumar concede 12 runs in a key middle-over.
Q: How does this affect DC's playoff chances? A: DC slip to 7th on 11 points and need 3 wins from 3 plus other results to qualify.
Q: Where can I see the full live archive? A: The full ball-by-ball is on our live page.
IPL 2026 Fantasy Tools
Share this article
Karthik Iyer
Expert in: Ipl 2026Cricket analyst and content writer at CricJosh, covering Ipl 2026 with 473 articles published.
Related Articles



6 min read ยท 30 April 2026
