Rohit Sharma out fourth straight match

Rohit Sharma’s injury has stopped being a one-match inconvenience. It now looks like a real stretch of missed time in the middle of Mumbai Indians’ season — and that matters because MI don’t have the luxury of cruising through it. On April 29, Rohit sat out again as Mumbai faced Sunrisers Hyderabad at Wankhede. That made it four straight missed matches, and Hardik Pandya made the key part plain at the toss: this is not over yet. (indianexpress.com) ### What changed on April 29? The fresh news was simple but important — Rohit was ruled out again before MI’s game against SRH, and Pandya said he would need “a couple more games” before he is ready. That pushes the timeline beyond the kind of short rest teams sometimes use to manage workload. It tells you Mumbai still think the hamstring is not where it needs to be for match play. (indianexpress.com)ack to April 12 against Royal Challengers Bengaluru. Rohit was 19 off 13 when he limped off and retired hurt during a chase of 241. The awkward part is that he had fielded through the RCB innings, so the issue either worsened later or became impossible to manage once he was batting at full intensity. Since then, he has not returned to the XI. (indianexpress.com)r? Because that phrase changes the story from day-to-day uncertainty to a likely medium absence. In cricket, hamstring problems are tricky — not because a player cannot jog, but because sprinting, turning, and explosive strokeplay are the real tests. A batter can look mostly fine in training and still not be ready for a live match. Pandya’s wording suggests Rohit is somewhere in that gap. (indianexpress.com) ### How much has MI felt it? Quite a bit. Mumbai put up 243/5 against Sunrisers, so the batting did not collapse on the night, but they still lost by 6 wickets with 8 balls left. That dropped them deeper into a rough season. Rohit’s absence is not the only reason MI are struggling, but it removes one of the few players who can settle an innings early and change the shape of the chase or powerplay. (espncricinfo.com)uns? Not really. Rohit’s value is also structural. He affects who opens, how aggressively MI start, and how much pressure lands on the middle order. When a senior opener goes missing, the rest of the lineup gets shuffled around him. That kind of disruption is manageable for a game or two. Four matches is where it starts to alter team planning. (sports.yahoo.com)nger one. That is the catch with this kind of injury — the player often feels close before he is actually safe to play at full speed. And for Mumbai, there is no point bringing Rohit back if he cannot run hard between the wickets or move freely in the field. (indianexpress.com)st public timeline is Pandya’s “a couple more games,” which means the wait is likely continuing into early May rather than ending immediately after the SRH match. Until Mumbai name him in the XI, the safest read is that recovery is still incomplete. (indianexpress.com)arma for four straight matches, their captain has hinted more are coming, and a shaky season now has one more problem it cannot solve quickly. (indianexpress.com)