NEW DELHI: Virat Kohli found himself at the centre of criticism after an unfortunate run-out involving Rajat Patidar during the Delhi Capitals (DC) vs Royal Challengers Bengaluru (RCB) match in IPL 2025 .
The incident happened in the fourth over of RCB’s innings when Kohli flicked a Mukesh Kumar delivery towards mid-wicket. Patidar, eager to steal a quick single, responded immediately but was sent back too late by Kohli.
Karun Nair, fielding at mid-wicket, showed great presence of mind.
Go Beyond The Boundary with our YouTube channel.
He collected the ball cleanly and fired a direct throw at the stumps, catching Patidar just short despite his desperate dive.
Patidar had to walk back for 6 runs off 6 balls, and fans were quick to blame Kohli for the confusion. Social media platforms were flooded with memes and angry reactions, roasting Kohli for the costly mix-up.
At that point, RCB’s score was a worrying 26/3 after 4 overs, with Kohli batting on 8 off 10 balls. It added further pressure to RCB's innings, which was already wobbling.
After the run-out, Kohli faced criticism online, with fans blaming him for the unfortunate dismissal.
Earlier in the match, RCB had done well with the ball. After winning the toss and choosing to bowl, they managed to restrict Delhi Capitals to 162/8. Josh Hazlewood led the charge with his tight lines, while spinners Suyash Sharma and Krunal Pandya slowed the scoring rate significantly during the middle overs.
KL Rahul was the top-scorer for DC with a patient 41 off 39 balls, but it was Tristan Stubbs’ late fireworks (34 off 18) that pushed DC to a fighting total.
Abhishek Porel gave DC a fast start with 28 off just 11 balls, but wickets kept falling at regular intervals. Only a strong finish in the last few overs, especially against Hazlewood and Yash Dayal, allowed Delhi to cross the 160-run mark.
With RCB chasing 163, Kohli’s mistake turned into a major talking point early in their innings.
The incident happened in the fourth over of RCB’s innings when Kohli flicked a Mukesh Kumar delivery towards mid-wicket. Patidar, eager to steal a quick single, responded immediately but was sent back too late by Kohli.
Karun Nair, fielding at mid-wicket, showed great presence of mind.
Go Beyond The Boundary with our YouTube channel.
He collected the ball cleanly and fired a direct throw at the stumps, catching Patidar just short despite his desperate dive.
Patidar had to walk back for 6 runs off 6 balls, and fans were quick to blame Kohli for the confusion. Social media platforms were flooded with memes and angry reactions, roasting Kohli for the costly mix-up.
At that point, RCB’s score was a worrying 26/3 after 4 overs, with Kohli batting on 8 off 10 balls. It added further pressure to RCB's innings, which was already wobbling.
After the run-out, Kohli faced criticism online, with fans blaming him for the unfortunate dismissal.
If you are batting with This man , You are destined to get Run Out .
— HomeLander_Raj (@RajHomelander) April 27, 2025
Virat Kohli the Run Outer 🥶🥶
Rajat patidar gone on 6(6) #DCvsRCB #RCBvsDC pic.twitter.com/493fdgwPFX
Kohli and run out..a better love story than Mughal-e-azam.#DCvsRCB #DCvRCB pic.twitter.com/M3w0Fkbb0y
— Ivaan (@Manish_LSG) April 27, 2025
Virat Kohli is a burden on his own team😂.
— Lord Kl Rahul (@temba215) April 27, 2025
Every time Virat Kohli run out his own team members 💔.#RCBvsDC | #TATAIPL2025 pic.twitter.com/yermfGPjLu
Kohli reaction on run out of captain #Rajatpatidar by #karunNair #viratkohli #DCvsRCB pic.twitter.com/YpeRPFCD6t
— 😃 Toffee ki Biwi coffee 😃 (@TDdyMalik128156) April 27, 2025
Terrific stuff from Karun Nair as Rajat Patidar was run-out!
— Cricketism (@MidnightMusinng) April 27, 2025
Another run out involving Virat Kohli. Just saying…#DCvRCB #DCvsRCB
pic.twitter.com/y23pad3Xn7
Earlier in the match, RCB had done well with the ball. After winning the toss and choosing to bowl, they managed to restrict Delhi Capitals to 162/8. Josh Hazlewood led the charge with his tight lines, while spinners Suyash Sharma and Krunal Pandya slowed the scoring rate significantly during the middle overs.
KL Rahul was the top-scorer for DC with a patient 41 off 39 balls, but it was Tristan Stubbs’ late fireworks (34 off 18) that pushed DC to a fighting total.
Abhishek Porel gave DC a fast start with 28 off just 11 balls, but wickets kept falling at regular intervals. Only a strong finish in the last few overs, especially against Hazlewood and Yash Dayal, allowed Delhi to cross the 160-run mark.
With RCB chasing 163, Kohli’s mistake turned into a major talking point early in their innings.
You may also like
Florida hit-and-run ferry crash: Mass casualty reported as boat collides near Clearwater, authorities hunt fleeing vessel
Liverpool news: Mohamed Salah makes admission as Arne Slot reveals Jurgen Klopp contact
Forza Horizon 5 PS5 release time – exactly when the former Xbox exclusive unlocks on PlayStation
ITV This Morning star breaks silence on axe by Keir Starmer in Labour admission
Tourist influx reduces in Jammu amid tensions over Pahalgam terror attack
