
Rohit Sharma smashed a 94-ball 155 while Virat Kohli scored 131 on his Vijay Hazare Trophy return.
Veteran batters Rohit Sharma and Virat Kohli delivered standout centuries on their return to the Vijay Hazare Trophy. Rohit guided Mumbai with a powerful 155 off 94 balls in Jaipur. He hit 18 fours and 9 sixes as Mumbai chased 237 with eight wickets in hand. The knock marked his first domestic List A appearance in seven years.
He reached his hundred in just 62 balls, marking his fastest century in the 50-over format. His previous best came in 63 balls against Afghanistan during the 2023 ODI World Cup in Delhi on October 11. Before this match, Rohit had scored only one Vijay Hazare Trophy century for Mumbai, which came on his debut in 2008.
In the match, Sikkim had earlier posted 236 for 7, with Mumbai captain Shardul Thakur taking two wickets. Rohit shared a brisk opening stand with Angkrish Raghuvanshi, who made 38, before Musheer Khan and Sarfaraz Khan completed the chase.
Rohit Sharma Century in Vijay Hazare trophy 🔥🔥#VijayHazareTrophy#RohitSharma #ViratKohli𓃵pic.twitter.com/dPkTO5GHwm
— SATYA ᴿᶜᴮ 🚩 (@sidhufromnaayak) December 24, 2025
Kohli Scores 131 in First Vijay Hazare Trophy Match in 15 Years
In Bengaluru, Kohli produced a composed 131 in his first Vijay Hazare match in 15 years. He anchored Delhi’s chase, providing the foundation for a comfortable win over Andhra. Delhi needed only 25 runs when Kohli departed. A brief wobble followed as Nitish Rana was dismissed for 77 and Rishabh Pant fell for 5 in quick succession. Badoni also departed soon after. Despite the late scare, Delhi completed the chase with four wickets in hand. Kohli ended as the top scorer.
READ ALSO | Sarfaraz Ahmed Takes a Jibe At Vaibhav Suryavanshi For Inappropriate Gestures
With this knock, Virat Kohli also became the fastest batter to reach 16,000 runs in men’s List A cricket.
THE VIRAT KOHLI CENTURY MOMENT.
— Mufaddal Vohra (@mufaddal_vohra) December 24, 2025
– 58th in List A cricket by the King. (Shashank Kishore).
pic.twitter.com/jo7UjmFkWs
This article follows WicketWatcher’s editorial standards. Learn more in our Editorial Policy or report an issue via our Corrections Policy.