The IPL has seen its share of nail-biters, but the April 18 clash between Royal Challengers Bengaluru and Delhi Capitals at M. Chinnaswamy Stadium delivered drama of the highest order. RCB had posted a competitive 175/8, only to watch DC scrape past the target with one ball to spare. Phil Salt nearly stole the show with a brutal 63 off 38, yet it was Tristan Stubbs’ composed 60 not out that sealed a famous chase for the visitors.

Don't miss these

4 related posts

Recent Match: IPL 2026 Match 26, April 18, 2026 · Venue: M.Chinnaswamy Stadium, Bengaluru · Head-to-Head Coverage: 18,154 T20 matches tracked · Key Event: RCB vs DC 26th Match scorecard · Upcoming: Match 39 Delhi Capitals vs RCB

Quick snapshot

1Confirmed facts
  • 31 matches played in IPL history between RCB and DC (MyKhel)
  • RCB won 20 of those 31 encounters, DC won 12 (MyKhel)
  • DC won Match 26 by 6 wickets at M.Chinnaswamy Stadium (IPLT20 Official)
2What’s unclear
  • Whether Phil Salt’s form carries into Match 39 given the narrow loss
  • How RCB adjusts bowling strategy with Bhuvneshwar Kumar’s heavy workload
  • DC’s rotation plans for Kuldeep Yadav ahead of the return fixture
3Timeline signal
  • IPL 2026 Match 26: April 18, 2026 — DC 177/4 beat RCB 175/8 by 6 wickets
  • Previous meeting: April 10, 2025 at M.Chinnaswamy Stadium
  • Return fixture: Match 39 (date TBA)
4What’s next
  • DC moves to 4th place with 6 points after the dramatic chase
  • RCB stays 2nd with 8 points but faces questions over bowling depth
  • Return fixture at Match 39 promises another tight contest
Field Value
League IPL 2026
Match Number 26th Match
Date April 18, 2026
Venue M.Chinnaswamy Stadium
Teams RCB vs DC
Result DC won by 6 wickets
Target chased 175
Player of Match Tristan Stubbs (DC)

Who won the match today RCB vs DC?

Delhi Capitals walked away with the win, clinching a thriller by 6 wickets at M.Chinnaswamy Stadium. The official match report from IPLT20 Official match coverage confirms DC chased down 175 with just one delivery remaining, finishing 177/4 in 19.5 overs. Tristan Stubbs anchored the chase with an unbeaten 60 off 47 balls, earning Player of the Match honors.

TATA IPL 2026 Match 26 Report

RCB’s innings got off to a flyer. Phil Salt blazed 63 off 38 balls at the top of the order, carting 4 boundaries and 3 sixes for a strike rate of 165.79, per CricTracker match statistics. He shared a 52-run opening stand with Virat Kohli in just 31 deliveries, setting a platform that looked capable of testing DC’s resolve.

Bhuvneshwar Kumar stood out with the ball for RCB, finishing 3/26 in his four overs, per CricTracker match statistics. Yet DC’s attack held serve when it mattered. Kuldeep Yadav, Axar Patel, and Lungi Ngidi each picked up two wickets to keep the scoring in check, as reported by CricTracker match statistics.

The upshot

Stubbs’ unbeaten 60 settled nerves that David Miller’s late surge had already calmed. Miller smashed 22 off just 10 balls — a strike rate of 220.00 — pulling 6, 6, and 4 off Shepherd in the final over to set the stage, per IPLT20 Official match coverage. When Stubbs finished the job, DC had completed a chase that looked shaky at the halfway mark.

The win pushed DC up to fourth place on the points table with 6 points, while RCB remained second with 8 points, per CricTracker match statistics.

Why is Salt not playing RCB vs DC?

Phil Salt was very much in the lineup for Match 26 — and delivered one of the performances of the night. He scored 63 off 38 balls with 4 boundaries and 3 sixes, nearly dragging RCB to a winning total before DC’s chase ultimately succeeded. The premise of the question appears to reference an earlier encounter; for the April 18 fixture, Salt was a confirmed starter.

DC vs RCB IPL 2025 Phil Salt absence

Historical records show Salt has featured in multiple RCB-DCs matchups across seasons. Per the verified match data from CricTracker match statistics, his opening partnership with Virat Kohli in Match 26 generated 52 runs in 31 balls — the kind of start that puts pressure on any bowling unit.

Salt’s strike rate of 165.79 reflects the controlled aggression that has defined