Chennai Super Kings beat Delhi Capitals by 23 runs in the 18th match of IPL 2026 at MA Chidambaram Stadium, Chennai, on April 11, 2026. Sanju Samson scored 115 not out off 56 balls, Ayush Mhatre added 59, and Jamie Overton claimed 4 wickets for 18 runs as CSK posted 212/2 and dismissed Delhi Capitals for 189.
Match at a Glance: Full Scorecard
The Delhi Capitals vs Chennai Super Kings match scorecard from the 18th match of IPL 2026 tells a story that goes beyond runs and wickets. A CSK side under pressure, a DC team that started well but unraveled at the worst moment, and one batter who made the game look unfairly simple.
| Detail | Information |
| Match | CSK vs DC, 18th Match, IPL 2026 |
| Venue | MA Chidambaram Stadium, Chepauk, Chennai |
| Date | April 11, 2026 |
| Toss | Delhi Capitals elected to field |
| CSK Score | 212/2 (20 overs) |
| DC Score | 189 all out (20 overs) |
| Result | Chennai Super Kings won by 23 runs |
| Player of the Match | Sanju Samson (115* off 56 balls) |
CSK Innings: When Samson Stopped Playing and Started Punishing
CSK scored 212/2 in 20 overs. Sanju Samson scored 115 not out off 56 balls with a strike rate above 205. Ayush Mhatre scored 59 off 36 balls. The two put on a partnership that effectively ended the match as a contest by the 15th over.
Delhi Capitals chose to field first. On a surface their captain described as slightly sluggish, it seemed like a defensible call. What no one in the DC camp had prepared for was Sanju Samson choosing to treat a slow track as a personal opportunity.
Sanju Samson: 115* off 56 Balls Calculated Destruction
This was not a lucky innings. Every shot had a purpose.
Samson finished with 15 fours and 4 sixes, striking at above 205. But the number that truly exposes how complete this knock was: an 89% control rate. That means 9 out of every 10 attacking shots went exactly where he intended. This was not slogging. A player slogging does not maintain 89% control across 56 deliveries.
What most people miss about this innings: Samson’s real damage did not happen in the powerplay. It happened in overs 9 to 14 the phase when most T20 batters take a breath, reset, and play rotation cricket. Samson accelerated. He scored at above 250 strike rate in that phase, specifically targeting DC’s medium-pacers through the off-side corridor. Their length planning became irrelevant because he was clearing the off-side field while stepping across his stumps.
Post-match, Samson described his mental state: “Basics are to get in a mentally different zone. Watch it come out nicely from the bowler’s hand.” That level of simplicity under pressure is a rare trait.
Samson’s control rate of 89% while striking above 200 is not a stat it is proof of intent.
Ayush Mhatre: The Composure No One Expected
The 19-year-old Ayush Mhatre scored 59 off 36 balls and, by Samson’s admission, “never looked like he was coming out of U-19.”
This was not an explosive cameo built on sixes. Mhatre rotated intelligently, picked his moments to attack, and built a partnership that gave Samson the freedom to play his natural game. The Samson-Mhatre partnership effectively ended the contest before the midpoint of the CSK innings. DC’s bowlers never recovered from the psychological blow of conceding 130-plus runs from that stand.
CSK Batting Scorecard
| Batter | Runs | Balls | 4s | 6s | SR | Dismissal |
| Sanju Samson* | 115 | 56 | 15 | 4 | ~205 | Not Out |
| Ayush Mhatre | 59 | 36 | — | — | ~164 | Dismissed |
| Ruturaj Gaikwad | — | — | — | — | — | — |
CSK Phase-by-Phase Scoring
| Phase | Overs | Runs | Wickets | Key Event |
| Powerplay | 1-6 | ~62 | 0 | Strong start, no early pressure |
| Middle Overs | 7-15 | ~105 | 1 | Samson-Mhatre partnership explodes |
| Death Overs | 16-20 | ~45 | 1 | Momentum maintained, platform held |
The Overton Blueprint: How CSK Dismantled DC’s Chase
Jamie Overton took 4 wickets for 18 runs in 4 overs with an economy of 4.5. His strategy hard back-of-a-length deliveries targeting the outside edge of right-handers broke the DC chase in the middle overs. Anshul Kamboj supported with 3/35.
A target of 213 is steep. It is not impossible. Delhi Capitals had the batting depth to attempt it. What they did not have an answer for was Jamie Overton bowling at sustained high pace on a surface with variable bounce.
Jamie Overton: 4/18 in 4 Overs A Spell That Ended the Chase
4 overs. 18 runs. 4 wickets. Economy: 4.5. In the context of a 212-run chase, those are extraordinary numbers.
Overton’s plan was not complicated but it was brilliantly precise. He bowled hard-length deliveries that either climbed sharply off the surface or skidded through. DC’s middle order, structured around aggressive cross-bat strokes, had no plan B. His dismissal pattern was consistent: targeting the outside edge of right-handed batters by angling the ball across their body from a high-release point.
Overton’s own words explain the strategy better than any analysis: “Just trying to hit the top of the stumps. Tried to reduce their cross-batted shots.”
That is a bowling masterclass compressed into one sentence. When a pitch has variable bounce and tacky conditions, removing the cross-bat option forces batters into technical positions where their errors multiply. That is exactly what happened to DC’s middle order.
A control rate above 80% in a death-bowling context from a pace bowler is elite-level execution.
CSK Bowling Figures
| Bowler | O | R | W | Econ |
| Jamie Overton | 4 | 18 | 4 | 4.5 |
| Anshul Kamboj | 4 | 35 | 3 | 8.75 |
| Noor Ahmad | 3 | 36 | 1 | 12.0 |
| Gurjapneet Singh | 4 | 39 | 1 | 9.75 |
| KK Ahmed | 3 | 40 | 1 | 13.33 |
CSK Bowling Phase Analysis
| Phase | Overs | Runs Conceded | Wickets | Strategy |
| Powerplay | 1-6 | 66 | 2 | Pressure maintained, DC settled |
| Middle Overs | 7-15 | ~78 | 6 | Overton cluster, chase collapsed |
| Death Overs | 16-20 | ~45 | 2 | Kamboj mop-up |
DC Innings Breakdown: Where the Batting Fell Apart
Delhi Capitals were bowled out for 189 in 20 overs while chasing 213. Despite a 61-run opening stand between Nissanka (41) and Rahul (18), DC lost 6 wickets between overs 7 and 15. Tristan Stubbs (60 off 38) was the only batter to show sustained intent.
Delhi Capitals were not outclassed at the start. They were outclassed at the moment it mattered.
The powerplay delivered 66 runs from 2 wickets a competitive platform. Pathum Nissanka scored 41 off 24 and KL Rahul contributed 18 off 10. That is a 61-run opening partnership. On most T20 nights, that foundation is enough to win.
This is where things went wrong.
The Middle-Over Collapse: A Slow Bleed
Between overs 7 and 15, DC lost 6 wickets for approximately 78 runs. This is the kind of collapse that does not look catastrophic in the highlights but is fatal in the scorebook. Every partnership lasted just long enough to build false confidence, then ended before it could change the match.
The common mistake analysts make is blaming the bowling. The real problem was a mentality mismatch in DC’s batting order. Multiple batters played as if someone else was responsible for winning the game. No one took ownership of the chase until Tristan Stubbs arrived by which point the required rate had climbed beyond the team’s collective ability.
DC captain Axar Patel identified a different root cause post-match: “The fielding was the difference. A couple of dropped catches had we taken them, it might have been different.” Those dropped catches in the CSK innings directly inflated the target from a potential 185-190 to 212. The damage was not done with the bat. It was done in the field, 40 overs earlier.
DC Full Batting Scorecard
| Batter | Runs | Balls | 4s | 6s | SR | Dismissal |
| Pathum Nissanka | 41 | 24 | — | — | ~171 | Caught |
| KL Rahul | 18 | 10 | — | — | ~180 | Caught |
| Sameer Rizvi | 6 | 9 | — | — | ~67 | Caught |
| Axar Patel (c) | 1 | 2 | — | — | ~50 | Caught |
| David Miller | 17 | 14 | — | — | ~121 | Bowled |
| Tristan Stubbs | 60 | 38 | — | — | ~158 | Caught |
| AR Sharma | 19 | 10 | — | — | ~190 | Caught |
| Auqib Nabi | 4 | 2 | — | — | — | Caught |
| Kuldeep Yadav | 4 | 7 | — | — | ~57 | Caught |
| L Ngidi | 3 | 5 | — | — | — | Caught |
| T Natarajan | 1* | 2 | — | — | — | Not Out |
| Extras | — | — | — | — | — | — |
| Total | 189 | 20 ov | — | — | — | All Out |
Fall of Wickets: 1st-61, 2nd-61, 3rd-66, 4th-76, 5th-121, 6th-149, 7th-154, 8th-183, 9th-185, 10th-189
DC Phase-by-Phase Scoring
| Phase | Overs | Runs | Wickets | Key Event |
| Powerplay | 1-6 | 66 | 2 | Strong start, Nissanka-Rahul |
| Middle Overs | 7-15 | ~78 | 6 | Cluster collapse, chase fractured |
| Death Overs | 16-20 | ~45 | 2 | Stubbs fights alone, too late |
Turning Points That Changed the Match
Three moments decided the Delhi Capitals vs Chennai Super Kings match. First, DC’s fielding errors gifted CSK 20-25 extra runs. Second, Samson’s acceleration in overs 9-14 removed DC’s momentum advantage. Third, Overton’s re-introduction at the point when DC’s middle order began fragmenting sealed the result.
Every T20 has one or two moments that decide the result before most viewers notice. This match had three.
Turning Point 1 The Dropped Catches
DC’s fielding errors during CSK’s innings are the most underreported story of this match. Axar Patel directly admitted the dropped catches changed the scoreline. In T20 cricket, fielding mistakes do not just cost runs they shift psychological momentum. When CSK batters survive chances, they bat with freedom. When DC fielders drop catches, they bowl with doubt.
The dropped catches alone likely cost DC 20-25 runs and elevated the target beyond a comfortable chase range.
Turning Point 2 Samson’s Acceleration in Overs 9-14
When DC expected the middle overs to provide breathing space, Samson made them the most expensive phase of the innings. The phase when DC should have been cutting the run rate became the phase where the game was irretrievably lost. CSK scored at approximately 12 runs per over across overs 9-14.
Turning Point 3 Overton’s Second Spell
Once KL Rahul was dismissed and DC’s middle order began to fragment, Ruturaj Gaikwad brought Overton back at the precisely right moment. The hard-length plan, re-established in DC’s middle overs, meant no lower-order partnership ever had the pace or platform to build. The re-introduction of Overton in overs 11-14 was the captain’s best decision of the match.
Read More About – Royal Challengers Bengaluru vs Mumbai Indians Match Scorecard IPL 2026: Full Stats, Turning Points, and Analysis
Why CSK Won and Why DC Lost
Why CSK Won
- Samson scored 115 not out with an 89% control rate
- Mhatre added 59 in a match-defining partnership
- DC dropped catches, inflating CSK’s total by 20-25 runs
- Overton’s 4/18 dismantled the DC middle order
- DC lost wickets in clusters, with no batter taking ownership of the chase
Why DC Lost
- Fielding failures during CSK’s innings directly inflated the target
- Middle-order mentality collapse no batter took individual responsibility
- No answer to Overton’s hard lengths from right-handed batters
- Powerplay momentum not converted 66/2 after 6 overs became 76/4 by over 10
- Axar Patel’s dismissal for 1 removed any hope of a captain’s rescue act
IPL 2026 Points Table Impact
After this win, CSK moved to 12 points from 11 matches in IPL 2026, sitting fifth on the table with a positive NRR of +0.185. DC dropped to 10 points from 12 matches with a damaging NRR of -0.993.
The Delhi Capitals vs Chennai Super Kings match scorecard result had significant points table consequences for both franchises.
| Team | M | W | L | Pts | NRR |
| RCB | 12 | 8 | 4 | 16 | +1.053 |
| GT | 12 | 8 | 4 | 16 | +0.551 |
| SRH | 12 | 7 | 5 | 14 | +0.331 |
| PBKS | 11 | 6 | 4 | 13 | +0.428 |
| CSK | 11 | 6 | 5 | 12 | +0.185 |
| RR | 11 | 6 | 5 | 12 | +0.082 |
| DC | 12 | 5 | 7 | 10 | -0.993 |
CSK’s win was more than two points. Their NRR improved into positive territory, which is a critical factor when playoff qualification comes down to decimal differences. For a team that had endured three consecutive losses, this result restored both mathematical standing and dressing room confidence.
For DC, the NRR of -0.993 is a red alarm. They do not just need wins in the remaining matches they need large wins. A defeat by 23 runs without a compensating run-rate improvement means DC must now outperform on both results and margins, which is a significantly harder task.
Fantasy Cricket Verdict
For DC vs CSK fantasy cricket, Sanju Samson is the top captaincy pick based on his 115-run performance. Jamie Overton is the highest-value differential bowling pick. Tristan Stubbs is a reliable DC accumulator. Avoid DC’s middle order (Rizvi to Axar Patel) in any fixture where CSK have pace-friendly conditions.
Building a fantasy team around the DC vs CSK IPL 2026 scorecard data reveals clear, data-backed patterns.
Captain and Vice-Captain Recommendations
- Sanju Samson (Captain) 115* off 56 balls, 89% control rate, premium pick in any Chepauk fixture
- Jamie Overton (Vice-Captain) 4/18 is not a one-off. When Chepauk offers hard-length assistance, Overton’s pace and angle are a wicket-taking combination
- Tristan Stubbs 60 off 38 in a losing cause. He scores even when the team does not. Strong points accumulator at low credit cost
Players to Avoid
- DC’s middle order (Rizvi to Axar Patel) multiple failures, low strike rates under pressure, no ownership of chase situations
- Bowlers conceding above 12 runs per over both Noor Ahmad and KK Ahmed went above 12 in economy. That is a points drain in fantasy formats
The most common fantasy mistake is picking famous names over in-form value. Overton’s 4/18 in this match generated more fantasy points than most DC batters combined at a fraction of the credit cost.
Frequently Asked Questions
Q1: What was the result of DC vs CSK 18th match IPL 2026?
Ans. Chennai Super Kings beat Delhi Capitals by 23 runs at MA Chidambaram Stadium, Chennai on April 11, 2026. CSK scored 212/2 and DC were bowled out for 189.
Q2: Who won the Player of the Match in CSK vs DC IPL 2026?
Ans. Sanju Samson was named Player of the Match for his innings of 115 not out off 56 balls, which included 15 fours and 4 sixes at a strike rate above 205.
Q3: What was Sanju Samson’s score against Delhi Capitals in IPL 2026?
Ans. Sanju Samson scored 115 not out off 56 balls with an 89% control rate and a strike rate of approximately 205 one of the best T20 innings of IPL 2026.
Q4: What were Jamie Overton’s bowling figures against DC in IPL 2026?
Ans. Jamie Overton took 4 wickets for 18 runs in 4 overs at an economy rate of 4.5 among the best bowling performances of the IPL 2026 season at the time.
Q5: What was the full Delhi Capitals vs Chennai Super Kings match scorecard in IPL 2026?
Ans. CSK: 212/2 in 20 overs (Samson 115*, Mhatre 59). DC: 189 all out in 20 overs (Stubbs 60, Nissanka 41). CSK won by 23 runs.
Q6: Who was the top scorer for Delhi Capitals against CSK in IPL 2026?
Ans. Tristan Stubbs top-scored for Delhi Capitals with 60 off 38 balls. Despite his effort, the rest of the batting order failed to support a chase of 213.
Q7: Why did Delhi Capitals lose to CSK in IPL 2026?
Ans. DC lost due to three connected reasons: poor fielding (dropped catches inflated CSK’s total), a middle-order collapse where no batter took ownership of the chase, and Jamie Overton’s 4/18 which dismantled any recovery attempt.
Q8: Who won the toss in CSK vs DC 18th match IPL 2026?
Ans. Delhi Capitals won the toss and elected to field first. CSK batted and scored 212/2 in 20 overs.
Q9: What was the partnership between Samson and Mhatre in the CSK vs DC match?
Ans. Sanju Samson and Ayush Mhatre put together a dominant partnership in the middle overs. Samson scored 115 not out and Mhatre contributed 59, combining for over 130 runs and effectively ending the match as a contest.
Q10: Where does CSK stand in the IPL 2026 points table after beating DC?
Ans. After beating DC, CSK moved to 12 points from 11 matches placed fifth in the IPL 2026 points table with a positive NRR of +0.185.

