To compound Mumbai Indians’ struggles, they face a massive injury scare ahead of their next IPL 2026 game against the Punjab Kings (PBKS) on Thursday. According to Cricbuzz, opening batter Rohit Sharma is set to undergo scans as the franchise will determine the severity of his hamstring injury sustained amid the game against the Royal Challengers Bengaluru (RCB) at the Wankhede Stadium on April 12, Sunday.
MI vs PBKS, IPL 2026: Will Rohit Sharma play Mumbai Indians’ next match?
The 38-year-old retired hurt when he was 19 off 13 deliveries in the game against the RCB due to the hamstring strain. His movement in the crease was also restricted, forcing him to walk off the field in the sixth over to never return again. Before retiring hurt, the right-handed batter was attended by the physio as it triggered a lengthy stoppage of the proceedings for the treatment. According to Cricbuzz, the scans will determine Rohit’s exact gravity of the injury and whether or not he will be able to partake in the match against the Punjab Kings on April 16, Thursday.
When asked teammate and West Indies hard-hitter Sherfane Rutherford, he stated, as quoted by Cricbuzz:
“I’m not entirely sure yet – perhaps it’s a bit of a hamstring issue – but I can’t say for certain. I was in the dugout, so I don’t have much information on it.”
What happened the last time Mumbai Indians and Punjab Kings met one another?
Mumbai Indians last locked horns against the Punjab Kings in the Qualifier 2 of IPL 2025 at the Narendra Modi Stadium in Ahmedabad. Suryakumar Yadav and Tilak Varma scored 44 runs each, while Naman Dhir played a cameo of 37 off 18 deliveries with seven fours to lift the five-time champions to 203/6 in 20 overs. But PBKS skipper Shreyas Iyer flattened the five-time champions with an unbeaten 87 to take their side past the finish line with one over and five wickets as they entered the final.
While Mumbai Indians have succumbed to three consecutive losses, Punjab Kings are yet to lose a game, winning three games, with the remaining one ending in no result.
