IPL 2026 Play of the Day: Two run-outs, one turning point as Angkrish's calls hurt KKR

In T20 cricket, games often turn not on big shots but on small moments, and Kolkata Knight Riders were left to rue a couple of those as a promising chase slipped away against Sunrisers Hyderabad at Eden Gardens, with young Angkrish Raghuvanshi caught in the middle of it all.

Chasing 226, KKR knew they needed a steady start and a clear head through the middle overs. Instead, they found themselves chasing the game early. Ajinkya Rahane’s slow start at the top did not help, his eight off 10 balls putting pressure on the rest, and when partnerships failed to build, IPL-2026-sunrisers-hyderabad-beat-kolkata-knight-riders-eden-kolkata-2890908-2026-04-02" target="_blank">the innings never really settled.

KKR vs SRH, IPL 2026: HIGHLIGHTS | SCORECARD

There was some early spark from Finn Allen, who looked in a hurry with a brisk 28 off seven balls, picking up from where he had left off at this venue not too long ago. But once he chipped one back to Harsh Dubey, the early momentum faded and KKR were left trying to piece things together.

That responsibility fell on Raghuvanshi. The 21-year-old looked assured, finding the gaps and keeping the scoreboard ticking. His 52 off 29 balls, with six fours and two sixes, gave KKR something to work with at a time when the chase could have drifted away.

But even as he was batting well, the first signs of trouble had already crept in.

TWO MOMENTS OF HARA-KIRI

Off Malinga’s over, a moment of confusion nearly cost KKR another wicket. Cameron Green drove the ball back towards the non-striker’s end and set off, while Raghuvanshi, caught in the line, struggled to get out of the way as the ball ricocheted off him. There was also a brief collision with Eshan Malinga, who was moving towards the ball. By the time Raghuvanshi looked up, Green was almost beside him, forcing a hurried call for the run. Malinga collected and threw to the keeper, but a slightly wayward effort and Raghuvanshi’s desperate dive just about saved him.

KKR, however, were not as fortunate on the very next ball.

Raghuvanshi once again drove it back towards the bowler and set off. This time, Malinga got a boot to the ball, stopping it close to the stumps. Both batters froze for a split second before deciding to go through with the run, but the hesitation proved costly. Malinga recovered quickly, picked up the ball, and broke the stumps. Initially, it appeared that Raghuvanshi, running towards the non-striker’s end, was out and he even began to walk back. But the TV umpire confirmed that the batters had not crossed at the moment the wicket was broken, meaning it was Green who had to depart.

Then came the moment that hurt KKR the most.

Watch the video here:

A ball pushed to backward point led to confusion once again. Rinku Singh set off, then stopped on seeing the fielder move in quickly. Raghuvanshi had already committed and was well past halfway. By the time he tried to turn back, it was too late. Malinga was sharp, the throw was accurate, and Raghuvanshi was run out for 52.

He paused briefly before walking back, as if going over the call in his head. Rinku Singh’s reaction captured the moment. There was visible frustration and a brief exchange, reflecting the significance of what had just unfolded. In a chase of this magnitude, partnerships rely as much on trust as they do on strokeplay, and that understanding had broken down at a critical point.

The experts watching on were clear in their assessment. Piyush Chawla said, “I think it was poor running. If you see, Cameron Green got involved in that mix-up where he lost his wicket. The ball was right there, yet he ran. After that, when he himself got run out, it was off a firmly played shot that went quickly straight to the fielder. He still went for the run, and if Rinku had committed, he would have been run out too. Then he had to turn back and had no chance of making it. So I think this made a huge difference, two big names getting run out.”

Sunil Gavaskar added, “And both times, I think you have to say it was Raghuvanshi. On both occasions, you would say so because, the first time, he was the one who initiated the run, which is why Cameron Green responded from the non-striker’s end. And the second time, as you said, there was no run in it at all.”

From 120 for 4 in 11 overs, KKR lost their way. Rinku fell soon after, and the rest followed in a hurry. There were a couple of late hits from Sunil Narine, but by then the game had already slipped out of their reach.

KKR were eventually bowled out for 161, well short of the target, slipping to their second successive defeat after faltering in a chase of 227 against Sunrisers Hyderabad at home.

For Raghuvanshi, it was one of those nights that will stay with him. He played well, showed intent, and looked in control for most of his innings, but two immature calls between the wickets changed everything. For KKR, it was a reminder that in a chase like this, it is not always the big shots you miss, but the small moments you get wrong.

IPL 2026 | IPL Schedule | IPL Points Table | IPL Videos | Cricket News | Live Score

- Ends

Click here to read article