Prince Yadav bowls Kohli for rare IPL chase duck

For once, the noise around Virat Kohli stopped before it could even begin.

The chase had barely opened when a 140.4 kph inswinger from Prince Yadav zipped in, beat Kohli’s judgement, and smashed into off stump. For Royal Challengers Bengaluru, it was not just an early wicket. It was the sight every chasing side fears, Kohli walking back without scoring.

That one ball changed the mood of the night. It also handed Virat Kohli an unwanted mark, his first duck while chasing in the IPL since 2017.

Prince Yadav owns the moment

Cricket loves its grand scripts, but it often turns on one plain delivery.

Prince Yadav did not need drama. He ran in during the second over, hit good pace, and got the ball to jag back sharply. Kohli looked set for the angle, then found himself beaten by movement.

For a young fast bowler, that wicket travels far. Kohli does not fall for ducks in chases often. In fact, since Dhawal Kulkarni in the 2016 IPL season, Prince became only the second bowler to dismiss Kohli for zero in that specific way in the tournament’s long memory.

That stat matters because Kohli has built a career on chases. He knows when to wait, when to punch gaps, and when to squeeze pressure back onto bowlers. So when he misses early, it feels bigger than one wicket.

For Royal Challengers Bengaluru, the damage was immediate. Their opening pair was gone for just 9 runs. In a shortened chase of 209 from 19 overs, that is like starting a race after stumbling at the blocks.

Marsh gives Lucknow the cushion

Before Kohli’s dismissal became the headline, Mitchell Marsh had already shaped the match.

Lucknow Super Giants reached a strong total after rain kept interrupting their innings. The game was reduced to 19 overs a side, but Lucknow did not bat like a team worried by breaks.

Marsh made 111, the kind of innings that makes a wet evening feel simple. He gave Lucknow both pace and structure. When a batter scores a century in a shortened T20 innings, he usually takes the match away from normal calculations.

Nicholas Pooran added 38, bringing his usual middle-overs punch. Captain Rishabh Pant stayed unbeaten on 32, useful runs because shortened games often reward every late boundary twice.

RCB’s bowlers did not have a complete collapse. Josh Hazlewood, Krunal Pandya, and Rasikh Salam Dar took 1 wicket each. But Lucknow kept finding enough runs between those wickets.

A target of 209 in 19 overs asks for almost 11 an over. That is possible in the IPL, but only if the chase starts cleanly. RCB got the exact opposite.

RCB rebuild, then stumble again

After Kohli went, RCB needed calm more than fireworks.

Rajat Patidar and Devdutt Padikkal tried to give them that. Their 95-run stand for the third wicket brought RCB back into the contest. It also reminded everyone why T20 chases cannot be read too early.

Patidar, as captain, had a double job. He had to score and also stop the innings from becoming messy. Padikkal had to keep the board moving without taking reckless risks.

For a while, it worked. The chase had rhythm again. Lucknow’s bowlers had to think, not just attack. RCB’s dugout had reason to believe.

Then Patidar fell, and the innings lost its spine. One wicket became another. That is the old T20 problem. A partnership can hide pressure, but it cannot erase the required rate.

Tim David gave the match late life with 40 from just 17 balls. Those are serious finishing numbers. He dragged RCB close enough to make Lucknow nervous.

But close is not enough when Duckworth-Lewis-Stern calculations enter the picture. Lucknow won by 9 runs through DLS, the rain rule used when weather changes a match’s length.

A rare Kohli failure stands out

Kohli’s duck will draw the most attention because rarity sells the story.

He has been in strong form this IPL 2026 season. That is why this dismissal feels sharper. A poor run can explain a cheap wicket. Form makes it surprising.

But there is a larger cricketing point here. Even the best chasers need those first 10 balls to read pace and movement. Prince Yadav gave Kohli no time to settle.

The ball also showed why genuine pace with inward movement remains priceless. A fast inswinger does not ask many questions. It asks one, very quickly. If the batter answers late, the stumps suffer.

For young Indian fast bowlers, this is exactly the sort of moment selectors notice. A wicket of Kohli is not just a scalp. It shows nerve, control, and the ability to beat a great player with skill.

Prince finished with 3 wickets, making his night much more than one famous delivery. Shahbaz Ahmed also took 2 wickets, helping Lucknow stop RCB’s middle order from fully taking charge.

Rain, pressure and small margins

Rain-hit T20 matches often look chaotic from outside. Teams stop, restart, recalculate, and change plans in minutes.

For batters, rhythm becomes harder. For bowlers, lengths change with the surface. For captains, every over feels like a small exam.

Lucknow handled that better. Marsh gave them a huge platform. Prince and Shahbaz then turned pressure into wickets.

RCB will look back at 2 phases. First, the opening collapse. Second, the wickets after the Patidar-Padikkal stand. In a chase that big, they could survive one bad phase. They could not survive two.

Fans may remember Kohli’s duck first, but the match was not lost by one man. It was lost in the small gaps between recovery and control. That is usually where tight IPL games slip away.

For Kohli, this will likely be treated as an odd blip. Great players carry long records because they rarely repeat the same mistake. For Prince Yadav, though, the night may become a career marker. In Indian cricket, one ball can open a door, but the next few matches decide whether it stays open.