DC vs GT Match Result: Gujarat Titans Beat Delhi Capitals by 1 Run in a Last-Ball IPL 2026 Thriller

DC vs GT Match Result: Gujarat Titans Edge Delhi Capitals by 1 Run in a Last-Ball IPL 2026 Classic 🏏🔥

Primary source pack provided in the attachment includes ESPNcricinfo/ESPN, SofaScore, LiveScore, and Cricbuzz links.

Match Summary

Gujarat Titans defeated Delhi Capitals by 1 run in the 14th match of IPL 2026 at Arun Jaitley Stadium, Delhi, on April 8, 2026. GT scored 210/4 in 20 overs, and DC replied with 209/8, falling short on the final ball in one of the tightest finishes of the season. Rashid Khan was named Player of the Match after returning figures of 4-0-17-3 in a game where almost everyone else disappeared under the run flow.

This was not a game where Delhi collapsed. This was a game where Delhi did almost enough, Gujarat held one phase better, and then the last over turned into pure nerve management. KL Rahul’s 92 off 52 kept the chase alive deep into the innings. David Miller’s 41 off 20* dragged the target to 2 needed from 2 balls. Yet GT still escaped because Prasidh Krishna held his nerve, Jos Buttler executed the final run-out, and Miller’s refusal of a single on ball five became the defining decision of the night.

Full Scorecard Snapshot 📊

Match Result Table

Top Batters

Key Bowling Figures

How Gujarat Titans Built 210/4 💥

Gujarat’s innings had balance. It did not depend on one hitter going berserk for 90-plus. It had layers. Shubman Gill made 70 off 45, returning after a neck issue and controlling the innings with timing rather than panic hitting. Jos Buttler added 52 off 27, an innings that mattered beyond the score because Gujarat needed him to look like a top-order match winner again. Washington Sundar’s 55 off 32 then gave the middle overs real force and prevented Delhi from dragging the scoring rate down. Reuters described it as a total built on a “trio of half-centuries,” and that is exactly what it was: three strong knocks, each taking over at the right time.

Gill later said GT believed 210 was around 10 to 15 runs above par on that surface. That detail matters. The wicket was not a flat arcade machine where anything under 220 was dead. Gujarat thought they had created a cushion. In hindsight, that assessment was correct by exactly one run.

Delhi still did decent work at the death. Reuters noted that GT managed only 58 runs in the final six overs, with Lungi Ngidi helping to drag the innings back into a manageable zone. That meant DC were not chasing a monstrous 225 or 230. They were chasing a total that required quality batting, not miracles.

Why GT’s batting innings worked

Delhi’s Chase Was Good Enough to Win Most Matches 😮

Delhi’s chase was not reckless. It was structured well for long stretches. KL Rahul and Pathum Nissanka added 76 for the first wicket, giving DC the exact launchpad needed in a 211 chase. Nissanka was the aggressor early, Rahul settled in, then accelerated. Reuters notes Rahul reached his fifty in 29 balls, and Cricbuzz’s post-match summary makes the same larger point: when wickets fell around him, he kept the run rate alive and prevented the chase from stalling completely.

The chase by phases explains the shape of the loss better than any dramatic narrative:

DC Chase by Phases

That middle block — overs 7 to 15 — lost Delhi the match. Not because 79 runs was terrible in isolation, but because they also lost 4 wickets there. A chase of 211 can survive one slowdown. It usually cannot survive four middle-overs wickets unless someone produces a freak finish.

KL Rahul nearly did. Miller almost finished it. But “almost” is the entire point of this match.

Rashid Khan Changed the Game 🌀

In a match where 419 runs were scored, Rashid Khan delivered 4 overs for 17 runs and 3 wickets. That is elite T20 bowling under extreme batting pressure. Cricbuzz’s post-match numbers show the wider contrast:

Spin Comparison

That table is the match in miniature. Gujarat’s spin unit created control. Delhi’s spin unit leaked momentum.

Reuters reported that Rashid’s burst removed Nitish Rana and Sameer Rizvi in successive deliveries, and later Axar Patel. Cricbuzz’s post-match section highlighted especially the Rizvi wicket and Rashid’s own satisfaction with beating a batter with the wrong’un. More important than names, though, was timing. Rashid did not just take wickets. He broke the chase at the exact stage when Delhi were trying to convert a solid platform into a winning position.

Why Rashid’s spell was decisive

• He bowled in a high-scoring match and still gave away almost nothing.
• He removed batters during the transition overs, not in dead phases.
• He forced DC to rebuild instead of keep attacking.
• He created scoreboard pressure that later made the final over so tense.

The Final Over, Ball by Ball 🎯

This is where the match entered IPL chaos territory.

Delhi needed 13 off the last over. GT were under an over-rate penalty, so the boundary setup was not ideal for them. Yet Prasidh Krishna still got through it. Reuters and Cricbuzz together outline the finish clearly.

Last Over Breakdown

The fifth ball will be replayed for a long time. Miller worked the ball into the leg side and declined the single, sending Kuldeep back. A single there would have leveled the scores and, at minimum, forced Gujarat to defend a tie on the last ball. Cricbuzz’s commentary states the obvious: Miller wanted to do it himself. He backed his boundary option. It failed.

Then the last ball: Prasidh bowled the slower short ball, Miller missed, Buttler gathered cleanly on the bounce and hit the stumps with an under-arm direct hit. Delhi briefly reviewed for a possible wide, but the ball was ruled legal; Cricbuzz records the tracking line as passing at 1.75 meters against Miller’s head height of 1.87 meters. Match over. Gujarat by one run.