New Delhi: The Board of Control for Cricket in India (BCCI) has firmly rejected speculation surrounding Rohit Sharma’s international future, with vice president Rajeev Shukla stating that there is “no question” of the Indian captain retiring from One Day Internationals.
Rumours over Rohit’s future gathered pace after reports suggested the ongoing ODI series against England could be his final assignment in the format. Speculation also claimed that the team management and selectors were looking beyond the 38 year old opener as they planned for the 2027 ODI World Cup.
However, Shukla dismissed the reports, saying Rohit continues to be an integral part of the Indian team and that the claims circulating on social media and in sections of the media have no basis. He reiterated that there is currently no discussion regarding the veteran batter’s retirement from ODI cricket.
The BCCI official also expressed confidence in the current team management and selection committee, stating that decisions on squad composition rest solely with the selectors. He added that with India continuing to perform well and register victories, there is no need for major changes in the side at present.
Rohit answered his critics with a commanding century in the series decider at Lord’s, smashing 138 runs off 110 deliveries. Although India ended up on the losing side, the innings underlined the opener’s ability to deliver on the biggest stage after modest scores in the first two matches of the series.
The latest clarification from the BCCI comes amid ongoing discussions about India’s long term plans for the 2027 World Cup, with younger players such as Yashasvi Jaiswal being viewed as potential future options. Even so, the board’s public backing suggests Rohit remains firmly in India’s plans for the immediate future.
Greater clarity over India’s ODI roadmap is expected when the team faces the West Indies in a three match ODI series in September, where Rohit’s role and the selectors’ long term strategy are likely to come into sharper focus.
Sorry, there was a YouTube error.
