“And our very own Rohit Sharma is back.” Even before stand-in captain Suryakumar Yadav completed those words for the seventh time out of eight, Wankhede Stadium had already turned into a roaring pressure cooker. A packed crowd at the unofficial spiritual home of Indian cricket—paying due respect to the grand legacy of Eden Gardens and the scale of the Narendra Modi Stadium—understood that Rohit’s return to the field would not have to wait much longer. After more than three weeks on the sidelines, the anticipation felt like it could be satisfied within a little over two hours.
Rohit made sure the wait was worth it. He started with patience, which was only natural given that he had been kept out of action for 21 days due to a hamstring injury. Once he felt settled—reading the pitch and tracking the bowlers—he accelerated in the manner that has become unmistakably his. On 15 runs off 15 balls, Rohit struck the second of his six boundaries, a pull over the fence off Avesh Khan. The momentum only grew from there. When he eventually departed, trapped by left-arm spinner M Siddharth, the damage had been done: the 39-year-old captain-in-waiting hammered a match-high 84 off 44 deliveries, a knock that kept Mumbai Indians in the playoff conversation, even if it still looks like a distant and slightly improbable dream.
This has been a strange chapter for Mumbai Indians. Their six-wicket demolition of Lucknow Super Giants on Monday night was only their third win in ten matches. If there were a trophy for the campaign’s biggest letdown, the franchise’s inconsistency would be hard to argue against. On paper, they possess a lineup built for destruction—batters with proven match-winning credentials, plus a pace unit led by Jasprit Bumrah and Trent Boult. Yet the IPL has never been a league where reputation automatically turns into results, and a strong squad does not always translate into steady success.
Rohit’s own season has mirrored that unpredictability. In the tournament opener for Mumbai against Kolkata Knight Riders on March 29, he struck 78 off 38 as part of an aggressive first-innings push of 148. That foundation, powered by a partnership with Ryan Rickelton, enabled Mumbai to chase down KKR’s 220 for four with five balls remaining. It also marked Rohit’s first competitive appearance since January 18, when he featured in the final of three One-Day Internationals against New Zealand. Even without match rhythm, the innings served as a declaration: the “old dog” still had fight in him.
Between those New Zealand ODIs and the start of the IPL, Rohit spent weeks working on his fitness. He shed more than 15 kilograms through a demanding program that combined high-repetition strength sessions with cardiovascular training. The transformation showed on the field—leaner movement, sharper intent, and the kind of quickness that suggested a player determined to prove he was not finished. With that mindset, he took apart a high-quality KKR bowling attack that featured Zimbabwean pace threat Blessing Muzarabani, a standout from the T20 World Cup, along with T20 spinner specialists Varun Chakravarthy and Sunil Narine.
The momentum looked promising when he followed up with 35 in the next match a week later against Delhi Capitals. But then came the setback. After a score of 5 against Rajasthan Royals, Rohit suffered the hamstring injury again on April 12 at Wankhede against holders Royal Challengers Bengaluru. He had to retire hurt early in the sixth over, with Mumbai beginning their chase strongly behind a 57-run opening stand with Rickelton. It was a blow that carried extra emotional weight for Mumbai, given that the franchise had moved on from him as captain ahead of the 2024 season, replacing him with Hardik Pandya—even though Rohit was still the Indian skipper at the time.
MI may have had their reasons, including the belief that Pandya represented the future and the desire to build a brand around him. Still, the way Rohit’s season turned abruptly made the separation sting. Rohit has kept a measured, dignified silence since then, but it would be hard to imagine it didn’t hurt. That same year, he responded with his first IPL century in a dozen years, scoring 417 runs in the competition, and he built on it last season by adding 418 runs, striking at a rate of 149.29. Those were his two best strike-rates across completed seasons. By IPL 2026, he had become a one-format international after retiring from both T20Is and Tests, making the opening statement against KKR feel more pointed—full of possibility.
Which is why his 84 on Monday should be read through a different lens. The innings was undeniably Rohit in its style, but what stood out most was the way timing and elegance took control in the middle overs. It wasn’t just a reminder of class; it also reflected appetite—hunger, resolve, and ambition. The fact that he took time to get set while facing a target of 229 highlighted experience and calm. It also demonstrated belief that a slow start could be converted into a meaningful finish. Then, once he sensed the gap, he burst through with two fours and two sixes off back-to-back deliveries from Avesh Khan, making it clear that forced time away had not dulled his destructive effectiveness.
Rohit did not rush himself back into the XI, nor did he get tempted into trying to be a hero while the team was trapped in a dreadful stretch. At this stage of his career, overreaching is not an option he can afford. Yet once he was confident about his fitness—and his ability to last for an innings, even if not necessarily the full duration of a match—he didn’t hold back. With him having played only half of Mumbai’s matches, he still ranks as the third-highest run-scorer in the side with 221 runs, behind only Rickelton (380) and Naman Dhir (256). In terms of maximum-hitters, only Rickelton has more sixes than Rohit’s 15. Time away hasn’t taken the edge off his competitive drive, and it hasn’t softened his ability to strike the ball with authority.
For now, the “Hitman” is not riding into the sunset. Not anytime soon.
