Beyond the Game
134

R. Ashwin reacts to fan’s comment on his emotional exit, reflecting on missed opportunities

Ravichandran Ashwin announced his retirement from international cricket after the third Test of the 2024-25 Border-Gavaskar Trophy. In response to a post from author K. Vaitheeswaran, who expressed regret over Ashwin’s retirement, Ashwin thanked him, saying, "The burden is over". Ashwin also shared he had no regrets about not leading India, despite early leadership roles in domestic cricket.

R Ashwin has retired from cricket and has no regrets about not captaining Indian team.
Image: R Ashwin has retired from cricket and has no regrets about not captaining Indian team / © The Week

With the end of the R. Ashwin era in international cricket, the 38-year-old announced his retirement after the third Test of the Border-Gavaskar Trophy 2024-25. His decision followed India’s win in Perth, Australia’s victory in Adelaide, and a draw in Brisbane.

Following his retirement announcement, Ashwin received emotional tributes, including a message from renowned author and former KSCA umpire K. Vaitheeswaran, who expressed sorrow, saying, “We are crying because it could have happened for a bit longer”. Ashwin replied to Vaitheeswaran, thanking him for his support and adding, “The burden is over”.

Ashwin also shared his contentment with his career, revealing that he had no regrets about not captaining the Indian team. He said:

I am smart enough to know what works for me and what doesn’t for another person. When I started my career, I got first-class captaincy very early. I have won a few tournaments for my team. I believe I had it in me. But I did not have any regret that I didn’t go on to lead my country because these are not things that I can control.

Despite leading various sides, he stated that the leadership of India wasn’t in his control, and he had no regrets about not getting the opportunity. This reflective phase marks the end of a distinguished career for the legendary off-spinner.

Comments

Thank you! We’re reviewing your comment.
We were unable to post your comment. Please, try again.