Mumbai Indians beat Lucknow by six

Mumbai Indians had no room left for a slow death. They needed a win, they needed it now, and they got the loudest version possible — a six-wicket chase of 229 against Lucknow Super Giants at Wankhede on May 4. That score usually buries teams. Mumbai ran it down with eight balls left. The big shift was simple: Rohit Sharma came back, Ryan Rickelton detonated the powerplay, and suddenly a season that looked finished had oxygen again. ### How big was this chase? Huge — it was Mumbai’s highest successful chase in the IPL, and the match aggregate hit 457 runs. Lucknow posted 228 for 5, which should have been enough on a lot of nights. But Mumbai finished on 229 for 4 in 18.4 overs, which tells you how hard they hit and how little control Lucknow had once the chase got moving. ### What did Rohit change? He changed the mood first, then the math. Rohit was playing his first match since April 12 and made 84 off 44 balls, which gave Mumbai something they’ve badly missed — a senior batter setting the pace instead of repairing damage. He wasn’t alone, but his return made the innings feel organized rather than desperate. ### Why was Rickelton the real wrecking ball? Because 83 off 32 bends the whole chase. Rickelton attacked so fast that 229 stopped feeling like a mountain and started feeling like a target with a short runway. ESPNcricinfo listed him as Player of the Match. ### Didn’t Lucknow already have enough runs? They should have. Nicholas Pooran made 63 off 21 balls with eight sixes, Mitchell Marsh added 44 off 25, and Lucknow were 123 for 1 by the eighth over. That is the kind of launch that usually sets up a winning, that missing extra 15 or 20 runs mattered. ### So did Mumbai bowl well or just survive? Mostly survive. Corbin Bosch’s 2 for 20 in two overs was the standout spell, and Raghu Sharma plus Allah Ghazanfar chipped in. But conceding 228 means the bowling questions did not disappear. Jasprit Bumrah leaked. That’s fine for one night. It’s a dangerous habit over a playoff run. ### What does this do to Lucknow? It makes a bad slide look brutal. This was Lucknow’s sixth straight loss. When a team scores 228 and still loses with eight balls left, that’s not bad luck anymore — that’s a side with no grip on matches. Rishabh Pant’s team keeps producing moments, especially through Pooran, but not enough control. ### Why does this matter for the table? Because Mumbai are still alive. Not safe — alive. This win keeps them in the playoff conversation, and doing it by chasing 229 so quickly also helps the one thing that starts deciding seasons at this stage: net run rate. Basically, Mumbai bought themselves another week of relevance. ### Bottom line? This was the version of Mumbai that always looked possible but rarely showed up together — Rohit steadying, Rickelton exploding, and the chase landing before panic could. But the warning label stays on the box: if you need 229 to cover your bowling, the margin is still thinner than the scorecard makes it look.