Eight for six. Read that again. That was Delhi Capitals’ score after 3.5 overs at their own home ground, in front of their own crowd, on a Monday night that was supposed to matter for their playoff hopes. By the time the powerplay ended, DC had effectively lost the match. What followed a meek chase completed by RCB inside 6.3 overs was just paperwork.
This is the full Delhi Capitals vs Royal Challengers Bengaluru match scorecard, broken down the way a scorecard alone never explains it: what happened, why it happened, and what it changed.
Match Snapshot
| Detail | Info |
|---|---|
| Match | 39th Match, Indian Premier League 2026 |
| Date | Monday, 27 April 2026 (Night match) |
| Venue | Arun Jaitley Stadium, Delhi |
| Toss | RCB won the toss, chose to field |
| Result | Royal Challengers Bengaluru won by 9 wickets |
| Player of the Match | Josh Hazlewood (4/12) |
This wasn’t a photo finish. It was a statement, and it needs to be read as one not as a routine defeat you shrug off after one bad night.
Full Scorecard: Delhi Capitals vs Royal Challengers Bengaluru
Delhi Capitals Batting Card: 75 all out (16.3 overs)
| Batter | Runs | Balls | 4s | 6s | SR | Dismissal |
|---|---|---|---|---|---|---|
| Sahil Parakh | 0 | 2 | 0 | 0 | 0.00 | b Bhuvneshwar |
| KL Rahul (wk) | 1 | 3 | 0 | 0 | 33.33 | c Jitesh b Hazlewood |
| Nitish Rana | 1 | 9 | 0 | 0 | 11.11 | c Padikkal b Hazlewood |
| Sameer Rizvi | 0 | 1 | 0 | 0 | 0.00 | c Jitesh b Hazlewood |
| Tristan Stubbs | 5 | 3 | 1 | 0 | 166.67 | c Padikkal b Bhuvneshwar |
| Axar Patel (c) | 0 | 3 | 0 | 0 | 0.00 | c Jitesh b Bhuvneshwar |
| Abishek Porel | 30 | 33 | 3 | 0 | 90.91 | b Hazlewood |
| David Miller | 19 | 18 | 3 | 0 | 105.56 | c Jitesh b Rasikh Salam |
| Kyle Jamieson | 12 | 13 | 1 | 1 | 92.31 | lbw b Krunal Pandya |
| Kuldeep Yadav | 3 | 11 | 0 | 0 | 27.27 | b Suyash Sharma |
| Dushmantha Chameera | 0 | 3 | 0 | 0 | 0.00 | not out |
| Extras | 4 (4 wides) | |||||
| Total | 75/10 | 16.3 overs |
Fall of wickets: 0-1 (0.2), 2-2 (1.1), 2-3 (1.2), 7-4 (2.1), 7-5 (2.4), 8-6 (3.5), 43-7 (8.6), 62-8 (12.3), 71-9 (15.3), 75-10 (16.3)
RCB Bowling Figures
| Bowler | Overs | Maidens | Runs | Wickets | Economy |
|---|---|---|---|---|---|
| Bhuvneshwar Kumar | 3 | 0 | 5 | 3 | 1.66 |
| Josh Hazlewood | 3.3 | 0 | 12 | 4 | 3.42 |
| Rasikh Salam | 2 | 0 | 21 | 1 | 10.50 |
| Romario Shepherd | 2 | 0 | 21 | 0 | 10.50 |
| Suyash Sharma | 4 | 1 | 7 | 1 | 1.75 |
| Krunal Pandya | 2 | 0 | 9 | 1 | 4.50 |
Read Also:- Lucknow Super Giants vs Punjab Kings Match Scorecard
Royal Challengers Bengaluru Batting Card: 77/1 (6.3 overs)
| Batter | Runs | Balls | 4s | 6s | SR | Dismissal |
|---|---|---|---|---|---|---|
| Jacob Bethell | 20 | 11 | 1 | 2 | 181.82 | c Natarajan b Jamieson |
| Virat Kohli | 23* | 15 | 1 | 2 | 153.33 | not out |
| Devdutt Padikkal | 34* | 13 | 3 | 3 | 261.54 | not out |
| Extras | 0 | |||||
| Total | 77/1 | 6.3 overs |
Fall of wickets: 26-1 (Jacob Bethell, 2.5 ov)
DC Bowling Figures
| Bowler | Overs | Maidens | Runs | Wickets | Economy |
|---|---|---|---|---|---|
| Kyle Jamieson | 3 | 0 | 42 | 1 | 14.00 |
| Dushmantha Chameera | 2 | 0 | 18 | 0 | 9.00 |
| Axar Patel | 1 | 0 | 5 | 0 | 5.00 |
| T Natarajan | 0.3 | 0 | 12 | 0 | 24.00 |
Key Moments: The Powerplay That Decided Everything
Here’s the thing most match reports get wrong: they treat this as a “batting collapse.” That’s technically true, but it hides the real story this was a new-ball execution masterclass, not a batting failure caused by nerves or pressure.
Bhuvneshwar Kumar opened with a wicket off the first over’s second ball Sahil Parakh bowled for a duck. Two balls later, Hazlewood struck twice in the same over, removing KL Rahul and Sameer Rizvi. By the end of over 3, DC were 8 for 6.
What most people miss: the ball wasn’t reversing or spitting off a demon pitch. Hazlewood’s own words afterward were blunt the surface was “skidding on quickly from short of a length,” and once it got soft, it flattened out. In other words, the conditions favored the bowlers for exactly six overs, and RCB’s attack read that window perfectly while DC’s top order didn’t adjust fast enough.
This is where things go wrong for teams every season: batting orders that don’t have a released “risk-manager” role for testing conditions. DC sent in the same aggressive top three they use against spin-heavy attacks, against two bowlers built specifically to swing a new ball in helpful conditions. That template mismatch not bad luck is what produced 8/6.
Player Performance Breakdown
Josh Hazlewood: The Wicket-Taker (4/12 in 3.3 overs)
Hazlewood’s spell wasn’t about pace.
It was about a single repeatable plan: straight lines in the corridor, forcing batters to play down the ground, backed by a hard short ball once the surface allowed bounce. Four wickets, twelve runs, and a Player-of-the-Match award that was decided inside the first six overs of the match not at the death.
Bhuvneshwar Kumar: The Enforcer (3/5 in 3 overs)
An economy of 1.66 in a T20 innings is not a normal outcome; it’s a statement. Bhuvneshwar’s figures matter more than Hazlewood’s in one specific way he set the tone with the very first over, and every DC batter walked in after that already one step behind.
Devdutt Padikkal & Virat Kohli: The Chase (34* off 13, 23* off 15)
Counterintuitive take: Padikkal, not Kohli, was RCB’s most destructive batter in the chase a strike rate of 261.54 against Kohli’s 153.33. The headline moment belonged to Kohli (his six off Natarajan brought up 9,000 IPL runs, a first for any batter), but the platform for that landmark was actually built by Padikkal’s lofted extra-cover hits off Kyle Jamieson.
Abishek Porel & David Miller: DC’s Lone Fightback (30 off 33, 19 off 18)
If there’s a silver lining in the scorecard, it’s this partnership. Porel and Miller together added 35 of DC’s 75 runs after the top six had combined for just 7. It didn’t change the result, but it stopped the innings from being a complete embarrassment DC’s lowest ebb of the season could have been worse.
Analysis: What Went Wrong for Delhi Capitals
What people think: DC lost the toss and got a bad batting surface.
Reality: RCB batted second on the same pitch and scored 77 in 6.3 overs at a run rate above 12. The surface was never the problem DC’s shot selection in the first three overs was.
Axar Patel admitted as much post-match: “If our openers or one of the top-order batters had negotiated those first couple of overs better, it could have made a difference.” That’s a captain conceding a strategic failure, not blaming conditions.
Common mistake teams make in this exact situation: sending out attacking batters against a fresh, swinging new ball without a plan to simply survive the first 12 balls. DC’s top four combined for 2 runs off 15 balls. Survival not aggression was the correct approach against Bhuvneshwar and Hazlewood in helpful conditions, and DC didn’t adapt.
Records Broken in This Match
| Record | Detail |
|---|---|
| Most balls remaining in a successful IPL chase (2nd all-time) | RCB won with 81 balls to spare (target 76) — behind only Mumbai Indians’ 87-ball win over Kolkata Knight Riders in 2008 |
| First batter to 9,000 IPL runs | Virat Kohli, reached with a six off T Natarajan in the 6th over |
| DC’s lowest powerplay score of the season | 8/6 inside the first six overs |
What This Result Means for the IPL 2026 Points Table
| Team | Matches | Won | Lost | Points | NRR | Position |
|---|---|---|---|---|---|---|
| RCB | 14 | 9 | 5 | 18 | +0.783 | 2nd |
| DC | 14 | 7 | 7 | 14 | -0.651 | 6th |
Read Also:- Sunrisers Hyderabad vs Delhi Capitals Match Scorecard
This wasn’t just a bad night it was DC’s third straight loss, and the NRR damage from a 9-wicket defeat is hard to reverse in a tight, congested mid-table. RCB, meanwhile, consolidated a top-two spot with a bowling attack that now looks like their biggest playoff weapon, not their batting depth.
Bold opinion worth stating plainly: DC’s problem this season isn’t personnel it’s game-state discipline. A side with Axar Patel, KL Rahul, and Tristan Stubbs shouldn’t be reduced to 8/6 by swing bowling in home conditions. That collapse is a tactical and temperament issue, and unless it’s fixed before their remaining fixtures, DC’s playoff hopes will keep eroding one bad powerplay at a time.
