365 articles generated
← Back to Feed
MatchupPlayerRetrospective

DC vs GT Retrospective: Rashid Khan's 3/17 and a Last-Ball Run-Out Stole the Thriller of the Season

DCGT
Wed Apr 08 2026 00:00:00 GMT+0000 (Coordinated Universal Time)9 min read
3/17Rashid Khan -- 100.7 impact, Player of the Match in 1-run thriller

1 Run. 1 Slower Bouncer. 1 Direct Hit. GT Stole What DC Had Earned.

KL Rahul scored 92(52) and still lost. David Miller was on 41* and standing at the striker's end for the final ball. DC needed 2 off the last delivery to win. Prasidh Krishna dug in a slower bouncer. Miller missed it. Jos Buttler hit the stumps direct from behind the keeper's end with Kuldeep Yadav stranded out of his ground. GT won by 1 run. It is the closest finish of IPL 2026 and the kind of match that makes you forget about models, probabilities, and projections for a moment. Then you remember: our model had DC at 62% favourites. The model was wrong.

GT get their first win of the season after an 0-2 start. DC suffer their first loss after a 2-0 opening. The standings just got interesting.

The Honest Model Check

What We SaidWhat HappenedVerdict
DC 62% favourites — strong callGT won by 1 run off the final ballThe model's second miss on a strong call this season. A 1-run margin means the probability was not wildly off, but the direction was wrong. DC were the better team for long stretches, and GT needed individual brilliance and a moment of fortune to win. Too early to call the model broken, but the strong calls are now 1 for 4.
DC's bowling as tournament-bestNgidi 66.9, Mukesh 38.7, Kuldeep 35.8 — all deliveredThis is no longer a projection. It is a fact. Across 3 matches, DC's bowling has been elite in every single game. Even in defeat, 3 bowlers posted above 35. The model's read on this unit has been correct every time.
Rashid Khan as GT's match-winnerRashid 3/17 with 100.7 impact — Player of the MatchExactly what the best players do. One performance does not validate a season-long projection, but Rashid's 100.7 in a match of this magnitude is a reminder of why the model rates him so highly.
KL Rahul projected as DC's batting anchorRahul 92(52) with 86.3 impactThe model had Rahul as DC's most important batter. He was. His 92 were the reason the chase reached the final ball. Sometimes the model gets the player right and the outcome still goes the other way.

What the Model Got Right

DC's bowling performed exactly as the model projected. Lungi Ngidi led with 66.9 impact, maintaining his position as one of the tournament's most effective seamers. Mukesh Kumar posted 38.7 impact for the third consecutive match of strong performance. Kuldeep Yadav's 35.8 impact demonstrated why left-arm wrist spin remains one of the most valuable skills in T20 cricket. T Natarajan added 24.8 impact, and even Axar Patel contributed a modest 1.8.

The one blemish was Vipraj Nigam at -5.7. After posting 32.2 impact against MI in match 8, this was a reminder that young bowlers have inconsistent nights. But one negative performance in a unit that produced four positive contributors is noise, not signal.

KL Rahul's performance was the other vindication. The model projects him as DC's highest-value batter, and his 92(52) with 86.3 impact was among the finest innings of the tournament. He batted through the middle overs with controlled aggression and accelerated when the equation demanded it. That he ended on the losing side despite this performance speaks entirely to the margins in this match, not to any failing on his part.

What the Model Got Wrong

The outcome. DC at 62% should win roughly 6 out of 10 times in this situation. GT winning is not an impossibility the model failed to account for. But the manner of the win exposed something the model does not capture well: moments of individual genius that override collective quality.

Rashid Khan's 3/17 was the intervention that separated the teams. His 100.7 impact is the fourth individual performance above 100 this IPL season. The model treats Rashid as an elite contributor. It does not have a mechanism for the specific match-turning spell where a bowler of his calibre picks apart a middle order in 4 overs and changes the entire trajectory of a chase. DC were building momentum when Rashid bowled. When he finished, they were rebuilding from wreckage.

Prasidh Krishna's 47.6 impact was concentrated in the moments that mattered most. His final over, defending a tiny margin, produced the slower bouncer that Miller could not connect with and the run-out that ended DC's season-opening unbeaten run. The model cannot project a bowler's ability to execute a specific delivery under that level of pressure. Some things remain beyond the reach of numbers.

The model also missed DC's middle-order fragility. Sameer Rizvi posted -2.4 impact after back-to-back Player of the Match performances. Nitish Rana's -3.5 impact continued his struggles. Rahul's 86.3 dominated DC's batting card so completely that the gap between him and the next contributor was enormous. Miller's 48.3 and Pathum Nissanka's 39.6 kept the chase alive, but the middle-order gaps were exposed at the worst possible time.

Rashid Khan: 100.7 Impact and the Match on His Shoulders

The numbers speak clearly. Rashid's 3/17 in 4 overs produced an impact of 100.7. This is the fourth time this season that an individual has crossed the 100 barrier, after Bishnoi's 109.7 in match 9, Shami's 104.2 in match 10, and Rizvi's 102.3 in match 8.

What separates Rashid's performance is context. GT were 0-2 and desperate. A third consecutive loss would have made their playoff path historically difficult. The match was in Delhi against a DC side that had won both their opening games and possessed the tournament's best bowling attack. Everything favoured DC. Rashid walked into that situation and turned it on its head.

His wickets came at critical junctures. Each dismissal disrupted a partnership that threatened to take the chase away from GT. The economy of 4.25 runs per over in a match that produced 419 total runs is extraordinary. He did not just slow the scoring. He stopped it.

GT's Innings: Buttler Built It, Washington Finished It

GT's 210/4 was a proper team effort. Jos Buttler's 52 produced 63.9 impact as the anchor. His innings set the platform that allowed others to play with freedom. Buttler's role as a measured accumulator who accelerates through the gears has been undervalued in discussions about GT's squad. This innings was a statement.

Shubman Gill's 70 posted 46.6 impact, a captain's knock that combined responsibility with intent. Washington Sundar then produced 55 with 48.7 total impact, an innings that pushed GT from a competitive total to an imposing one. Three half-centuries in a single innings is rare. It speaks to the quality GT have when their top five all contribute.

B Sai Sudharsan added 10.1 impact, and Glenn Phillips managed 5.1. Rahul Tewatia's -0.7 was the only negative. GT's batting depth functioned exactly as designed: multiple contributors rather than dependence on a single performer.

The Final Over: Cricket at Its Most Cruel

DC needed 12 off the final over. Miller had been striking cleanly at 41* impact. The equation was gettable. The crowd at Arun Jaitley believed. Prasidh Krishna believed otherwise.

His slower bouncer on the final delivery was the kind of execution that separates good death bowlers from clutch ones. Miller swung and missed. The ball went through to the keeper. Kuldeep Yadav backed up too far, as batters do when the equation demands every possible run. Buttler gathered and threw down the stumps in one motion. Kuldeep was out of his ground. GT had won by 1 run. Prasidh finished with 47.6 impact, the majority of it earned in those last 6 balls.

For DC, it was the cruellest possible ending to a match they had controlled for large stretches. Rahul's 92 deserved to be on the winning side. It was not. That is T20 cricket's brutal honesty: the best individual performance does not always win the match. Sometimes a direct hit from the boundary does.

Match Impact Scores

The impact model evaluates every delivery in context, measuring how much each player shifted the match outcome. A score above 50 represents a strong game. Above 75 is dominant.

GT -- Batting

PlayerRoleImpact
Jos ButtlerBatting63.9
Washington SundarBatting48.7
Shubman Gill (c)Batting46.6
B Sai SudharsanBatting10.1
Glenn PhillipsBatting5.1
Rahul TewatiaBatting-0.7

GT -- Bowling

PlayerRoleImpact
Rashid KhanBowling100.7
Prasidh KrishnaBowling47.6
Kagiso RabadaBowling27.7
Mohammed SirajBowling26.5
Ashok SharmaBowling-11.1

DC -- Batting

PlayerRoleImpact
KL Rahul (c)Batting86.3
David MillerBatting48.3
Pathum NissankaBatting39.6
Sameer RizviBatting-2.4
Nitish RanaBatting-3.5

DC -- Bowling

PlayerRoleImpact
Lungi NgidiBowling66.9
Mukesh KumarBowling38.7
Kuldeep YadavBowling35.8
T NatarajanBowling24.8
Axar PatelBowling1.8
Vipraj NigamBowling-5.7

The impact distribution reveals a match decided by one extraordinary individual. Rashid's 100.7 dwarfed everything else on GT's bowling card. DC had the more balanced bowling unit, with 3 contributors above 35 compared to GT's reliance on Rashid and Prasidh. But balance does not beat genius when the genius shows up at the right time.

What Comes Next

GT breathe. An 0-3 start would have been devastating. Instead, they sit at 1-2 with proof that when Rashid fires, this team can beat anyone. The batting showed depth with three half-centuries. The question is whether the bowling beyond Rashid can be consistent enough to compete when he has quieter days. Rabada and Siraj both contributed positively, which is encouraging. Ashok Sharma's -11.1 is the obvious concern.

DC at 2-1 will be frustrated but not panicked. Their bowling continues to be the best in the tournament. That is not debatable after three matches of evidence. The batting concern is Rizvi's -2.4 and Rana's -3.5. If Rahul has to score 92 every time DC chase, the model will eventually be right that they are vulnerable. But a team whose captain posts 86.3 in a losing cause and whose bowling posts 66.9, 38.7, and 35.8 in the same match is not a team in trouble. They are a team that lost by 1 run.

The model's strong calls are now 1 for 4 this season. The 62% DC call joins the 70% MI call (match 8), the 68% GT call (match 4), and the match 2 MI call as the only strong predictions. Only the MI-KKR call has held. The model's confident picks are its biggest weakness. We keep tracking. The data keeps humbling us.

Final Score: GT 210/4 (20 ov) beat DC 209/8 (20 ov) by 1 run

Rashid Khan: 3/17, 100.7. When the tournament needed a classic, he delivered one.

Comments0
Loading comments...