Kolkata Knight Riders Vs Chennai Super Kings Match Scorecard: Full IPL 2026 Breakdown

KKR were 79/2 after nine overs, chasing 193, with Ajinkya Rahane and Angkrish Raghuvanshi both looking settled. Then three wickets fell for 6 runs in under two overs, and the chase never recovered. A target that looked entirely gettable at the halfway mark ended 32 runs short. That collapse, not the final scoreline, is the real story of this match.

Which CSK vs KKR Match Are You Looking For?

CSK and KKR have met repeatedly across IPL seasons, and search results for this keyword often blend three different years together a 2021 meeting, two 2025 fixtures, and this IPL 2026 match. This article covers the 2026 result, played on 14 April 2026 at MA Chidambaram Stadium, Chennai Match 22 of the season. If a scorecard you find elsewhere shows different player names like Faf du Plessis or MS Dhoni in the XI, you’re looking at an older season, not this one.

Match Result and Full Scorecard

Kolkata Knight Riders won the toss and chose to field first.

Final result: Chennai Super Kings won by 32 runs.

Chennai Super Kings innings: 192/5 (20 overs)

Batter	Dismissal	Runs	Balls	4s	6s	SR
Ruturaj Gaikwad (c)	c R Powell b Anukul Roy	7	6	1	0	116.67
Ayush Mhatre	—	38	17	—	—	—
Sanju Samson (wk)	—	48	32	—	—	150.00
Sarfaraz Khan	—	—	—	—	—	—
Dewald Brevis	c V Arora b K Tyagi	41	29	4	2	141.38

Extras: not fully itemised in source. Fall of wickets: 25-1 (Gaikwad, 2.2 ov), 72-2 (Mhatre, 5.6 ov), 111-3 (Samson, 11.2 ov), 162-4 (Sarfaraz, 16.1 ov), 171-5 (Brevis, 17.3 ov). CSK finished 192/5 with Shivam Dube and the finishers unbeaten.

KKR bowling: Sunil Narine 4-0-21-1, Kartik Tyagi 4-0-35-2, Anukul Roy 1 wicket, plus Varun Chakaravarthy, Vaibhav Arora and Cameron Green sharing the remaining overs.

Kolkata Knight Riders innings: 160/7 (20 overs)

Batter	Dismissal	Runs	Balls	4s	6s	SR
Finn Allen	c Shivam Dube b Anshul Kamboj	1	3	0	0	33.33
Sunil Narine	c Gurjapneet Singh b Khaleel Ahmed	24	17	2	2	141.17
Ajinkya Rahane (c)	c Ruturaj Gaikwad b Noor Ahmad	28	22	0	2	127.27
Angkrish Raghuvanshi (wk)	c Dewald Brevis b Akeal Hosein	27	19	3	1	142.10
Rinku Singh	c Shivam Dube b Noor Ahmad	6	12	0	0	50.00
Cameron Green	b Noor Ahmad	0	1	0	0	0.00
Rovman Powell	not out	31	22	1	2	140.90
Ramandeep Singh	c Sarfaraz Khan b Anshul Kamboj	35	23	4	1	152.17
Anukul Roy	not out	1	1	0	0	100.00

Read Also:- Delhi Capitals Vs Rajasthan Royals Match Scorecard

Extras: 7. Fall of wickets: 13-1 (Allen, 1.4 ov), 29-2 (Narine, 4.2 ov), 79-3 (Raghuvanshi, 9.3 ov), 85-4 (Rahane, 10.5 ov), 85-5 (Green, 11.0 ov), 90-6 (Rinku, 12.5 ov), 153-7 (Ramandeep, 19.3 ov).

CSK bowling: Khaleel Ahmed 3.5-0-24-1, Anshul Kamboj 4-0-32-2, Akeal Hosein 4-0-26-1, Noor Ahmad 4-0-21-3, Gurjapneet Singh 1.1-0-23-0, Jamie Overton 3-0-32-0. Player of the Match: Noor Ahmad.

The Turning Point: Noor Ahmad’s Match-Winning Spell

Here’s what most recaps get wrong. They say “KKR never got going” and move on. But here’s the real problem KKR were actually 79/2 after nine overs, right on par with a 193 chase. This was not a one-sided contest from ball one.

What most people miss is exactly how it fell apart. Between the 9.3-over mark and the 11-over mark,

KKR lost three wickets for just 6 runs: Angkrish Raghuvanshi at 79, Ajinkya Rahane at 85, and Cameron Green at 85. Noor Ahmad accounted for two of those three, using flight and turn to draw mistimed shots rather than relying on pace off the pitch. In humid, dew-friendly conditions where gripping the ball is difficult, Ahmad specifically said afterward he focused on “keeping his fingers dry” a small, practical adjustment that directly explains why his control held up while others around him leaked boundaries.

Counterintuitive idea worth stating plainly: conventional T20 wisdom says spinners struggle in high-dew, high-humidity night games because the ball skids off wet fingers. Noor Ahmad’s 3/21 in exactly those conditions proves that preparation and grip management can neutralize that disadvantage entirely this wasn’t a spinner surviving difficult conditions, it was a spinner turning them into an advantage.

Player Performance Breakdown

• Noor Ahmad (3/21, Player of the Match): His three wickets came inside a five-over spell that directly created KKR’s 85/5 collapse.
• Practical takeaway for any legspinner bowling in the middle overs: Ahmad didn’t chase wickets with risky variations he built pressure with consistent flight and let batters make the mistake attempting to break free.
• Sanju Samson (48 off 32): Samson’s innings, built around a 47-run stand with Ayush Mhatre, gave CSK the platform to reach a genuinely defendable total.
• What people think vs reality: a 48 at a strike rate of 150 looks unremarkable next to bigger scores elsewhere in the match, but it was the innings that turned an average start (25/1 after 2.2 overs) into a competitive position by the halfway mark.
• Dewald Brevis (41 off 29): Brevis added the finishing touch CSK needed after Samson’s dismissal, striking two sixes in his knock to push the total from a modest 160-ish projection closer to 190-plus.
• Common mistake teams make against a settled middle order: KKR’s bowlers gave Brevis width during his innings instead of forcing him to manufacture his own boundaries, and he punished exactly that.
• Ramandeep Singh (35 off 23): The most underrated innings of the match by any competitor’s coverage. Coming in after KKR’s 90/6 collapse, Ramandeep’s 35 with 4 fours and a six was the only real fight KKR showed in the back half of their chase, briefly threatening to make the finish uncomfortable for CSK.
• Rovman Powell (31* off 22): Powell’s unbeaten innings kept KKR’s total respectable rather than embarrassing, but it came too late and with too few wickets in hand to seriously threaten CSK’s total.
• Ajinkya Rahane (28 off 22): As captain, his dismissal at 85/4 caught by his opposite number Ruturaj Gaikwad off Noor Ahmad was the psychological blow that opened the door for the middle-overs collapse.
• Bold opinion worth stating plainly: KKR’s chase was always going to hinge on Rahane or Raghuvanshi batting deep into the innings, and losing both inside six balls of each other made the eventual defeat close to inevitable.

What KKR Got Right and Still Lost

It would be lazy to write this off as a one-sided CSK win. KKR made real decisions that nearly worked.

What KKR Did Right	Why It Still Wasn’t Enough
Reached 79/2 in 9 overs, on pace with the target	Lost 3 wickets for 6 runs immediately after, wiping out the good start
Ramandeep Singh’s 35 off 23 rebuilt momentum after 90/6	The rebuild started too late, with too few overs and wickets remaining
Rovman Powell finished unbeaten on 31	A finisher batting to the end usually signals a near-miss, but KKR needed two such partnerships, not one
Sunil Narine’s 24 off 17 gave an early spark	His dismissal at 29/2 handed the innings’ shape to Rahane and Raghuvanshi too early

Read Also:- Punjab Kings Vs Delhi Capitals Match Scorecard

Bold opinion worth stating plainly: KKR’s problem in this match wasn’t a lack of individual quality every specialist batter in their top seven has match-winning ability on their day. The problem was sequencing. Two set batters got out within six deliveries of each other in the exact overs where CSK’s spin attack was operating at its sharpest. That is a tactical vulnerability, not a talent gap, and it’s a far more useful diagnosis than simply calling this a “comfortable” 32-run win.

Key Highlights and Records From the Match

• Chennai Super Kings won by 32 runs, restricting Kolkata Knight Riders to 160/7 after posting 192/5.
• Noor Ahmad won Player of the Match with figures of 3/21 in his four overs, his best bowling return of the season to that point.
• KKR lost 3 wickets for just 6 runs between the 9th and 11th overs of their chase, the decisive passage of the match.
• Sanju Samson and Ayush Mhatre added 47 runs off 22 balls for CSK’s second wicket, rebuilding after an early setback.
• Ramandeep Singh’s 35 off 23 was KKR’s joint-highest score of the innings alongside Rahane’s 28, despite coming in after a top-order collapse.

Frequently Asked Questions (FAQs)