RCB post a mammoth 250 and outclass CSK by 43 runs as Tim David’s explosive knock headlines a dominant performance.
Royal Challengers Bengaluru delivered a batting spectacle at the M. Chinnaswamy Stadium, posting a massive 250/3 against Chennai Super Kings in Match 11 of IPL 2026.
After being put in to bat, RCB got off to a brisk start with Phil Salt scoring 46 off 30 balls, while Virat Kohli added 28 off 18. The momentum continued through Devdutt Padikkal, who struck a fluent 50 off 29 deliveries.
However, it was the late onslaught that completely turned the game in RCB’s favour. Captain Rajat Patidar played a sensational unbeaten knock of 48 off just 19 balls, while Tim David stole the show with a blistering 70* off 25 balls at a staggering strike rate of 280.00. His innings, laced with eight sixes, dismantled the CSK bowling attack, especially in the death overs.
ALSO READ | IPL 2026 | SRH Dominate KKR At Eden Gardens After Travis Head-Abhishek Sharma Show
Among the bowlers, Anshul Kamboj, Jamie Overton, and Shivam Dube managed to pick up a wicket each, but the overall bowling effort lacked control as RCB maintained a run rate of 12.50.
CSK’s Fight Falls Short Despite Middle-Order Resistance
Chasing a daunting 251, CSK had a disastrous start, losing Ruturaj Gaikwad, Sanju Samson, and Ayush Mhatre inside the first three overs.
A counterattack came from Sarfaraz Khan, who smashed 50 off just 25 balls, injecting momentum into the chase. Contributions from Prashant Veer (43 off 29) and Jamie Overton (37 off 16) kept CSK in the hunt, but the required rate continued to climb.
RCB’s bowlers maintained pressure throughout, with Bhuvneshwar Kumar leading the attack with figures of 3/41. Jacob Duffy and Krunal Pandya picked up two wickets each, while Abhinandan Singh and Suyash Sharma chipped in with crucial breakthroughs.
Despite crossing the 200-run mark, CSK were eventually bowled out for 207 in 19.4 overs. RCB secured a commanding 43-run victory, showcasing their batting firepower and climbing momentum in IPL 2026.
This article follows WicketWatcher’s editorial standards. Learn more in our Editorial Policy or report an issue via our Corrections Policy.