Sunrisers Hyderabad vs KKR Match Scorecard IPL 2026

Chasing had ruled IPL 2026 — until Sunrisers Hyderabad flipped the script. In Match 6 at Eden Gardens on April 2, 2026, SRH posted 226/8 and then suffocated Kolkata Knight Riders’ chase until the hosts folded for just 161. The result gave SRH something no team had managed in the young season: a successful defense.

SRH Score: 226/8 (20 overs) · KKR Score: 161/10 · Result: SRH won by 65 runs · Player of the Match Hint: H Klaasen 50 off 34 · Venue: Kolkata

The following table summarizes the official match record as verified across multiple sources.

What is the SRH highest score?

SRH posted 226 for 8 in their 20 overs at Eden Gardens — their highest total of IPL 2026 so far. Travis Head and Abhishek Sharma gave the innings its early thrust, adding 52 runs in just 4.1 overs with a 50-run opening stand. Head was dropped on 34 by KKR captain Ajinkya Rahane at the 3.5-over mark, a miss that proved costly. Head fell at 82-1 in the 5.4th over. SRH crossed 100 three balls into the 9th over but lost Abhishek at 112-3 in the 8.4th over.

SRH innings breakdown

The SRH innings followed a familiar IPL template: explosive start, mini-consolidation, then another surge. After Head’s exit, the middle order kept the runs flowing without fully capitalising. Heinrich Klaasen changed that in the closing overs, striking 50 off just 34 balls before being caught at 222-7 in the 19.4th over. Shivang Kumar was dismissed on the last ball of the innings, with SRH at 226-8.

Top scorers for SRH

Klaasen’s 50 off 34 led the charge, combining power hitting with the ability to find gaps. Head’s early 34 laid the foundation before his dismissal. The supporting cast — including Nitish Reddy’s sensible knock and Harsh Dubey’s useful runs in the final overs — ensured SRH reached a total their bowlers could work with.

What are the weaknesses of SRH?

Even in victory, cracks showed. Head’s early drop — a straightforward chance put down by Rahane — gave SRH a life they shouldn’t have needed. Without that reprieve, the 82-run opening stand looks different, and Klaasen’s lower-order heroics alone may not have compensated. The early tournament history for SRH includes some abysmal totals, making the 226 a welcome outlier rather than a trend.

Batting vulnerabilities

SRH’s batting has shown a tendency to lose quick wickets in the middle overs — a pattern that almost cost them here. When Head fell at 82-1, the next highest score from the remaining lineup was modest by comparison. If Klaasen hadn’t delivered at the death, 226 would have looked very different.

Bowling issues

SRH’s bowlers held under pressure today, but the attack lacks a consistent wicket-taker in powerplay situations. The KKR chase started with 52 runs needed inside 5 overs — the kind of start that usually spelled trouble for SRH in earlier IPL 2026 matches.

Can Sunrisers Hyderabad’s batting firepower crack 300?

226/8 falls short of 300 — but not by much. With Klaasen in form and Head capable of anchoring a long innings, SRH has the ingredients for a record-breaking total. The question is whether the batting order beyond the core performers can sustain pressure once the top order falls cheaply.

Batting strengths shown

SRH demonstrated maximum firepower across the innings. Head and Sharma put on 52 in the first five overs. Klaasen’s 34-ball 50 showed peak strike rate capability. The 226 total — while not 300 — was the highest SRH had posted in IPL 2026 and the first time their batting clicked across all phases.

Close to record in this match

The 226 total sits comfortably above the IPL average for successful chases at Eden Gardens, but reaching 300 would require an entirely different gear. SRH would need their top four to fire simultaneously and sustain a run rate above 15 for the full 20 overs — a scenario that remains theoretical without more evidence from this season.

Who won the SRH vs KKR match?

Sunrisers Hyderabad beat Kolkata Knight Riders by 65 runs in Match 6 of IPL 2026 on April 2 at Eden Gardens. KKR won the toss and chose to field first, a decision that backfired as SRH built 226/8. KKR’s chase then crumbled under pressure, folded for 161 in just 16 overs. SRH became the first team to successfully defend a total in IPL 2026, breaking the season-long trend of chasing teams dominating.

Final scores

SRH closed their innings at 226/8 in the full 20 overs. KKR managed only 161 before being bowled out in the 16th over — still four overs in hand but comprehensively short of the target. The 65-run margin reflected SRH’s dominance across both innings.

Margin of victory

The 65-run win was decisive by any measure. KKR’s batting lineup never looked comfortable after losing early wickets. Jaydev Unadkat’s final-over burst — including cleaning up Varun Chakravarthy with a yorker — sealed the result with overs to spare.

What is the full SRH vs KKR scorecard?

The official match scorecard shows SRH’s 226/8 built through consistent scoring across all phases, while KKR’s 161 was shaped by a top-order collapse that started before the halfway point of their chase. Key milestones include Head’s dropped catch at 34 and the 50-run opening stand that set SRH’s tempo.

Batting scorecard

SRH’s leading scorer was Heinrich Klaasen with 50 off 34 balls, followed by Travis Head whose 34 laid the platform before his dismissal at the 5.4-over mark. Abhishek Sharma contributed before falling at 112-3 in the 8.4th over. KKR’s best individual score came from their middle order, though no single batsman reached 40 in a chase that required urgency from ball one.

Bowling scorecard

KKR’s bowling attack took 8 wickets but conceded 226 runs — a cost per wicket that made their target impossible. SRH’s bowlers were more economical, wrapping up KKR’s innings inside 16 overs with a combined effort led by Jaydev Unadkat’s decisive final over.

Fall of wickets

For SRH: 52-0 (4.1 ov), 82-1 (5.4 ov), 112-3 (8.4 ov), 222-7 (19.4 ov), 226-8 (19.6 ov). For KKR: 50-1 (3.2 ov), 100-3 (8.4 ov), 161-10 (16 ov). KKR lost three wickets between 50 and 100 runs — a window where a steady rebuild should have happened but didn’t.