KKR finds themselves under early pressure after a second straight defeat in IPL 2026, this time failing to chase down a daunting 227 set by Sunrisers Hyderabad at Eden Gardens. On a batting-friendly surface, the margin for error was minimal, and they fell short again.
At the center of it sits Rinku Singh, whose inability to influence the chase once he arrived before the death overs is becoming increasingly hard to ignore. The pattern is not surprising anymore. It is a flaw that opposition teams are beginning to exploit with clarity again and again.
KKR Ignoring the Obvious? Rinku Singh Misused in a Role That Blunts His Biggest Strength
KKR continue to raise eyebrows with how they are using Rinku Singh with the bat. Walking in right after the powerplay against Sunrisers Hyderabad, he was left to navigate the entire middle phase, an area that has never been his strongest suit in T20 cricket, especially in high-pressure chases.
This was not a situation forced by collapse either. At just three wickets down and with a healthy run rate, KKR had room to continue with someone else. Sending Rinku Singh that early felt like a tactical misread, exposing him to phases where his natural tempo and boundary-hitting rhythm tend to dip significantly.
Rinku Singh's performance in middle-overs and death overs in IPL
Overs
Average
Strike-rate
7-16
29.6
118.4
17-20
31.4
193.8
Even though he managed a strike-rate of 140 on the night, the larger trend remains concerning. With an IPL career middle-overs strike-rate of 118.4, KKR are ignoring clear evidence. Continuing with this approach risks neutralizing one of their most dangerous finishers, Rinku Singh, whose strike-rate rockets to 193.8 in IPL death overs.
For a player like Rinku Singh, entry point is not a minor detail, it is everything in T20 cricket. His game is built for the last five overs, not for rebuilding phases. Yet KKR continues to push him into situations that blunt his biggest strength repeatedly in the ongoing IPL 2026.
Against Sunrisers Hyderabad, it happened again. Sent in right after the powerplay, Rinku was forced to navigate the middle-overs instead of finishing the chase. It is a recurring pattern now, and unsurprisingly, he has not been the match-winner in chases for KKR since the 2023 season.
The numbers back the concern. In successful chases over the last two seasons, Rinku has managed just 31 runs across three innings at a strike rate of 110.71. While wins often mask individual roles, this raises a bigger question, what happens when the team actually needs him to deliver?
Rinku Singh's in last 5 unsuccessful chases for KKR
Entry Point
Runs
15 overs
38* off 15
9.1 overs
2 off 9
11.3 overs
17 off 14
7.5 overs
9 off 6
6 overs
35 off 25
The answer lies in the losses. Since last season, in chases KKR lost, Rinku Singh's entry point in the last five overs happened only once, and he smashed an unbeaten 38 off 15. Every other time, he came in too early and failed to get going, including last night against Sunrisers Hyderabad, leaving no finisher alongside Ramandeep Singh.
What Are the Solutions? Time Running Out for KKR to Fix the Rinku Puzzle
One immediate fix for KKR could have been promoting Anukul Roy. Coming off a stellar domestic season with Jharkhand, he offers both accumulation and intent in the middle-overs, exactly the move needed to delay Rinku Singh’s entry into his ideal phase.
Another intriguing option lies in one of KKR's hidden gems Tejasvi Dahiya, a Delhi keeper-batter who has shown promise in navigating middle-overs in domestic circuits and the Delhi Premier League. Including such a profile could unlock a more defined, effective role for Rinku Singh.
Tejasvi Dahiya T20 stats
Tournaments
Matches
Batting Average
Strike Rate
SMAT 2025
4
56.50
168.66
DPL 2025
10
48.43
190.45
DPL 2024
10
20.80
163.78
There is also the Cameron Green factor. Him not bowling limits balance, possibly forcing conservative selections over flexible batting roles. If Green begins contributing with the ball, KKR could free up combinations, but the concern remains whether these changes might come a little too late.