Sunrisers chase 244, beat Mumbai Indians

This was IPL excess in its purest form — 492 runs, four wickets in the chase, and a target of 244 that still wasn’t enough. Mumbai Indians did plenty right at Wankhede on April 29. Ryan Rickelton played the innings of his IPL career. But Sunrisers Hyderabad treated 12.2 an over like a manageable asking rate, got home in 18.4 overs, and left Mumbai with the kind of loss that messes with your whole sense of what a winning total even is. (espncricinfo.com) ### How big was Mumbai’s total, really? Huge. Mumbai made 243/5, which in most T20 games is game over. Rickelton carried the innings with 123 not out from 55 balls, smashing 10 fours and 8 sixes. Will Jacks gave him a flying start with 46 off 22, and Hardik Pandya’s 31 off 15 kep(espncricinfo.com 1)(espncricinfo.com 2) ### So how did Hyderabad keep up? They did it the SRH way — attack first, ask questions later. Travis Head ripped into the chase with 76, Abhishek Sharma added 45, and the platform never really dipped. Hyderabad were not rebuilding at any stage. They were just moving the target line backward ball by ball until Mumbai’s total stopped looking massive and started looking vulnerable. (cricbuzz.com) ### Where did the game actually turn? Klaasen made sure there was no wobble. His unbeaten 65 off 30 was the finishing blow, and Salil Arora’s 30 not out off 10 made the end feel brutal rather than tense. Hyderabad still needed clean hitting deep into the chase, but Mumbai never found the over that slowed thi(cricbuzz.com). (cricbuzz.com) ### Why does this hurt Mumbai so much? Because 243 should buy you control. Instead, Mumbai’s bowlers were dragged into a game where even decent overs felt irrelevant. Jasprit Bumrah and Trent Boult are supposed to be the reset buttons in chaos, but Hyderabad’s batting kept the pressure on so hard that the usual hierarchy of a T20 innings disappeared. When a side loses after 243, the batting unit can’t really be blamed. (espncricinfo.com) ### Why does it matter for Hyderabad beyond one win? This was Hyderabad’s fifth straight win, which is the part that turns a wild chase into a standings story. A one-off 244 chase is spectacle. Doing it in the middle of a winning streak says something more serious — this lineup is peaking, and it can win from positions where most teams are still doing damage control arithmetic. (espn.com) ### Was this just flat-pitch nonsense? Partly, sure — Wankhede was quick, true, and unforgiving for bowlers. But 244 still does not chase itself. Plenty of teams cash in on conditions and still fall 15 short because the middle overs stall or the finishers misread one matchup. Hyderabad didn’t do that. They kept intent all the way through, which is much harder than just swinging on a road. (espncricinfo.com) ### What’s the bigger IPL takeaway? The ceiling keeps moving. Totals that used to end games now just set up them up. Hyderabad’s chase was the highest successful T20 chase at Wankhede, and one of the biggest in IPL history. That doesn’t just make for highlights — it changes how teams think about batting first, bowling changes, and what counts as scoreboard pressure at all. (espn.com) ### Bottom line? Mumbai produced a near-perfect batting night and still lost by six wickets. Hyderabad didn’t just chase 244 — they made it look like the modern IPL version of par. (espncricinfo.com)