Rohit Sharma had to leave the game while batting, having scored 19 runs from 13 balls as Mumbai Indians were trying to get 241 which Royal Challengers Bengaluru had set at the Wankhede Stadium on April 12th. He looked good at the beginning of the innings, but then pulled his hamstring and asked for medical help.
Match context and RCB batting dominance
Royal Challengers Bengaluru scored a very large 240 for four wickets, with quick scoring at the start and smart batting in the middle of their innings. Phil Salt and Virat Kohli put on 120 runs for the first wicket, immediately putting Mumbai under pressure. Kohli and Rajat Patidar then continued to score steadily through the middle overs.
Tim David finished the innings strongly with 34 runs not out, taking the total over 240. The Mumbai bowlers did get some wickets – Trent Boult, Hardik Pandya, Mitchell Santner, and Shardul Thakur each took one – but didn’t manage to put much pressure on RCB early on. This huge score meant Mumbai had a very difficult chase in front of their home fans.
Sequence of events leading to Rohit Sharma retiring hurt
Rohit Sharma and Ryan Rickelton got Mumbai off to a good start, with 62 runs in the first six overs. Rohit was hitting the ball well and scored 19 runs from 13 balls. But in the sixth over he suddenly asked for someone from the team to come to the side of the pitch and got attention from medics because he seemed to have pulled his hamstring when running between the wickets.
The team doctor quickly checked Rohit, and he clearly wasn’t feeling good. He decided to ‘retire hurt’ and go off the field. According to the rules of cricket, a batter who retires hurt can come back later in the innings if they are able to, so although he left immediately, it wasn’t meant to be a permanent exit from the game.
Immediate medical assessment and visible concern
The medical team looked at Rohit on the field and he walked off slowly, not putting much weight on his leg. Hamstring injuries are tricky because they can get worse if you try to play on them, and this is especially true in a busy tournament like the IPL. Everyone on the team and the fans were worried as he left the field, and his family in the crowd were looking on nervously.
Hardik Pandya (the captain) and the Mumbai team management will get scans and a more thorough look at the injury to see how serious it is. At the moment they haven’t said what ‘grade’ the hamstring pull is, but teams are usually careful and don’t take risks with these injuries to avoid even longer absences.
Immediate tactical impact on Mumbai Indians’ chase
Because Rohit had to leave the game early, Suryakumar Yadav had to come in to bat sooner than expected, and it changed Mumbai’s plans for the chase. Losing a captain and an experienced opening batter stops the team’s flow and means people have to do different jobs in the batting order, and all this when they’re chasing 241 at the Wankhede.
This meant the middle-order batters had to start scoring quickly and not lose many wickets. Mumbai didn’t have much room to make mistakes; they needed to score at a good pace but also make sure they weren’t getting out, and they needed to do this without Rohit, who normally keeps things steady at the top of the innings.
Outlook for Rohit Sharma and IPL scheduling concerns
Hamstring injuries usually need several weeks of work to get better, though a less serious pull might only take a few days of rest and treatment. Because the IPL has so many games close together, there are concerns about whether Rohit will be able to play in the next matches. Mumbai will look at the scan results before saying when he might be back. Being careful is important to avoid it happening again and to protect his fitness for the long term.
‘Retiring hurt’ means Rohit is allowed to continue his innings later if he feels well enough. For now, Mumbai Indians will focus on getting a good medical evaluation, giving Rohit a specific plan for getting back to fitness, and controlling how much he does, so he can play in the rest of the tournament without making the injury worse.
