SRH cracks highest chase at Wankhede
- Sunrisers Hyderabad chased 244 to beat Mumbai Indians by six wickets at Wankhede on April 29, powered by Travis Head and Heinrich Klaasen. - Mumbai still made 243 for 5, with Ryan Rickelton blasting 123 not out, but SRH replied with 249 for 4 in 18.4 overs. - The win lifted SRH into the top three and deepened Mumbai’s slide, with the playoff race now tightening around net run rate.
IPL games are supposed to bend toward chaos late, but this one basically started there. Mumbai Indians put up 243 for 5 at Wankhede — a total that usually ends the argument. Sunrisers Hyderabad treated it like a target worth attacking harder, not respecting more. By the 19th over, they were home at 249 for 4, and the ground had just seen the highest successful T20 chase it has ever hosted. (iplt20.com) ### How big was this chase? Huge — even by IPL standards that have gotten a little numb to 220-plus scores. SRH’s 244-run chase was the fourth-highest successful chase in IPL history, and the biggest ever in any T20 at Wankhede. The game also produced 32 sixes, the most in an IPL match at the venue. (espncri([iplt20.com)e-1534547)) ### Didn’t Mumbai bat well enough to win? More than well enough, normally. Ryan Rickelton made 123 not out from 55 balls — ESPNcricinfo lists it as the highest score by a Mumbai Indians batter in IPL history — and Will Jacks added 46 as MI reached 243 for 5. The weird part is that 243 beca(espncricinfo.com)ace-on hitting took over. (espncricinfo.com) ### So how did SRH pull it off? They split the chase into waves. Travis Head gave them the violent start with 76, Abhishek Sharma kept the tempo moving with 45, and then Heinrich Klaasen finished it off with 65 not out from 30 balls. That last stretch matt(espncricinfo.com)diculous when the asking rate starts above 12 an over. (espncricinfo.com) ### Why does Wankhede matter here? Because Wankhede is already known as a batting ground, so breaking records there means you cleared a very high bar. This wasn’t some one-off on a tiny outground. It happened at one of the IPL’s most familiar high-scoring (espncricinfo.com). (espncricinfo.com) ### Was this just bad bowling? Partly, but that’s too simple. Even Jasprit Bumrah had a rough night, which tells you the conditions and the hitting were both extreme. ESPNcricinfo’s stats note called it a day to forget for bowlers across the board. When top-end death bowling still doesn’t slow the chase, the batting side is doing more than cashing in on mistakes — it’s dictating terms. (espncricinfo.com) ### What does this do to the table? It gives SRH real momentum and a much stronger playoff position. The updated standings after Match 41 moved Sunrisers into the top three, while Mumbai stayed down in ninth after a sixth defeat. That matters because the middle of the table is crowded now (espncricinfo.com)(sports.yahoo.com) ### Why does this feel bigger than one result? Because it says something about both teams at once. SRH look like a side that can win from almost any match state if the top order gets a foothold. Mumbai look like a team that can produce a once-a-season innings from Rickelton and still not control the game. That’s the difference between a contender and a side chasing the season. (espncricinfo.com) ### Bottom line? Mumbai scored 243 and still lost comfortably enough for the margin to feel clarifying. SRH didn’t steal this — they overran it, and now the playoff math around them looks a lot more dangerous for everyone else. (espncricinfo.com)