With a win becoming just a formality towards the end of the India’s run-chase of Bangladesh’s 256/8, the fans were still chewing their nails because the runs needed by Kohli to complete his 48th ODI century and India to complete a victory were near identical.
Kohli (103* off 97 balls) eventually finished it with a six and sparked festivities among the Indian cricket fans around the world. En route to that century, Kohli also became the fastest to complete 26,000 international runs.
Here’s how his former teammates and fans reacted on social media:
★Former cricketer Sachin Tendulkar tweeted, “Another day, another century! Congratulations Virat Kohli on your 48th ODI hundred, and becoming the fastest to 26,000 runs. Keep going strong!”
★Former Indian captain Sourav Ganguly wrote, “What a player! What a century! Well done Virat Kohli. Keep the runs flowing.”
★Cricketer-turned-commentator Virender Sehwag tweeted, “Kohli, you beauty! Well played, champion. Congratulations on another century.”
★Indian cricket fan Rajesh Sharma said, “Virat Kohli never fails to amaze us with his batting skills. He truly is a legend of the game.”
★Another fan, Priya Singh, added, “Watching Kohli play is always a treat. He makes it look so effortless. Congrats on the century!”
Kohli’s century not only secured a win for India but also showcased his exceptional talent and determination on the field. His performance has once again solidified his position as one of the best batsmen in the world.
Summary:
★Indian cricket fans celebrated as Virat Kohli completed his century and led India to a seven-wicket victory over Bangladesh in the ICC World Cup.
★Kohli’s century also made him the fastest player to reach 26,000 international runs.
★Former teammates and fans took to social media to congratulate Kohli on his achievement and praise his batting skills.
Follow DelhiBreakings on Google News
Superfast News Coverage by DelhiBreakings.com team.
For Superfast national news and Delhi Breaking Stories visit us daily at https://delhibreakings.com
Something went wrong. Please refresh the page and/or try again.
