Prince Yadav stuns Kohli with 140 kph duck dismissal

A 140.4 kph ball can make even a great batter look late.

That is what happened to Virat Kohli in a chase where RCB needed calm, control, and one familiar hand on the wheel. Instead, the ball jagged in, hit off-stump, and left the stadium briefly stunned.

Kohli walked back for 0 against Lucknow Super Giants. For most batters, that is just another bad night. For Kohli, it becomes a statistic people remember.

Prince Yadav finds the perfect ball

The wicket came in the second over, when Prince Yadav got one to swing in sharply. Kohli misread the line, and the ball did the rest.

It was not a loose shot or a slog gone wrong. It was a proper fast bowler’s dismissal. Full enough, quick enough, and late enough to beat a top-class player.

The speed, 140.4 kph, matters here. At that pace, a batter has almost no time to correct a small mistake. Kohli’s front foot moved, but the ball kept coming in.

For a young bowler, this is the kind of wicket that travels quickly. Dismissing Kohli for 0 in a chase is not routine IPL currency. It gets remembered in dressing rooms.

It also put RCB under pressure almost immediately. A chase of 209 in 19 overs already demands a clean start. Losing Kohli that early changes the mood of the innings.

A rare Kohli chasing failure

Kohli has built half his legend on run chases. He reads targets like a banker reads interest rates. He knows when to absorb pressure and when to squeeze the field.

That is why this duck stood out. It was his first duck while chasing in the IPL since 2017. For a player so closely linked with calculated chases, that is a long gap.

The number also tells us something about his consistency. In T20 cricket, openers and top-order batters take risks early. They face the new ball, attacking fields, and hard lengths.

Yet Kohli has avoided this kind of early exit for years. That is not luck. It comes from method, balance, and a sharp sense of where the danger sits.

This season, he had also been in strong scoring touch. So the dismissal felt sharper because it broke a pattern. Cricket fans notice when a familiar script suddenly tears.

There is another small slice of history here. Since Dhawal Kulkarni in the 2016 IPL season, Prince became only the second bowler to dismiss Kohli for 0 in this manner.

That is a heavy line on any young bowler’s resume. But it also brings attention, pressure, and video analysis. The next team will study him more carefully.

Marsh gives Lucknow a mountain

Lucknow did not win only because Kohli failed. They first built a total that gave their bowlers room to attack.

Rain interrupted the Lucknow innings more than once. The match then became a 19-over contest for both sides. In that shortened frame, Lucknow still reached 208.

Mitchell Marsh played the innings that shaped the night. His 111 gave Lucknow both speed and weight. It was the kind of hundred that hurts a chasing side mentally.

A T20 hundred in a reduced match changes everything. It means one batter has controlled almost the whole innings. It also means the bowlers never found a settled plan.

Nicholas Pooran added 38, which kept the tempo high. Captain Rishabh Pant finished unbeaten on 32, giving Lucknow the final push they needed.

For RCB, Josh Hazlewood, Krunal Pandya, and Rasikh Salam Dar took 1 wicket each. But those wickets did not slow Lucknow enough. The total had already stretched beyond comfort.

A target of 209 in 19 overs asks for more than good batting. It asks for sustained risk. Every quiet over feels expensive, and every wicket feels twice as damaging.

RCB fight, then stumble

RCB’s chase began badly. Both openers were back with only 9 runs on the board. In a chase this steep, that is almost like starting with a puncture.

Rajat Patidar and Devdutt Padikkal then gave the innings some shape. Their 95-run stand for the third wicket brought RCB back into the match.

That partnership mattered because it stopped panic. Patidar took responsibility, while Padikkal helped rebuild the chase. For a while, Lucknow had to think again.

But T20 chases often turn in one over. Once Patidar fell, RCB lost wickets in clusters. The pressure moved from the scoreboard to the dressing room.

Tim David tried to drag the match back with raw power. His 40 from 17 balls gave RCB a late chance and some noise in the stands.

But cameos do not always cover early damage. Lucknow kept finding wickets at the right time. Prince finished with 3 wickets, while Shahbaz Ahmed took 2.

Lucknow eventually won by 9 runs under the DLS method. That margin tells its own story. RCB were not miles away, but they were never fully in control either.

Selection rooms will notice

Matches like this travel beyond the points table. Coaches will look at Marsh’s hundred, Prince’s new-ball spell, and RCB’s middle-overs wobble.

For Lucknow, the result gives them more than 2 points. It gives them evidence that their younger bowling options can win hard moments.

That is valuable in the IPL. Big names fill the posters, but seasons often turn on lesser-known players handling pressure. Prince did that against one of cricket’s biggest names.

For RCB, the concern is not Kohli’s duck alone. Even great players fail. The bigger question is how often the side depends on one calm innings to hold a chase together.

Patidar and Padikkal showed fight. David showed hitting power. But RCB still need a cleaner batting chain when the target climbs above 200.

For fans, this match had everything the IPL sells every summer. A famous batter beaten early, a young bowler making a name, and a chase that stayed alive late.

But beneath the noise sits a simple reminder. T20 cricket may love sixes, but one good ball still changes a night. For Kohli, it was a rare low. For Prince Yadav, it may become the spell people mention first when they talk about where his IPL story truly began.