bettingidindia.xyz

MI vs SRH Lowest Team Scores and Batting Collapses

MI vs SRH Lowest Team Scores and Batting Collapses
Mumbai Indians were bowled out for 87 in 18.5 overs at Wankhede Stadium on 24 April 2018. It is the lowest team total in their IPL rivalry. Sunrisers Hyderabad’s lowest against MI is 96 all out in 17.4 overs, recorded in Hyderabad on 6 April 2019. Both innings show how quickly an ordinary target can become impossible when wickets fall together.

The rivalry is famous for huge totals, but the small scores tell a very different story. In 2018, SRH defended only 118 and still won by 31 runs. In 2019, MI defended 136/7 after a record bowling spell. These matches are useful because they show what happened, when the batting broke down and why the result did not follow the size of the first-innings total.

Lowest in rivalry87MI · 2018
SRH lowest vs MI962019 · Hyderabad
MI’s other sub-100922016 · Visakhapatnam
118 defended31SRH’s winning margin in 2018

MI vs SRH Lowest Score: The Five Smallest All-Out Totals

The table below ranks the five lowest all-out innings in completed MI–SRH IPL meetings through the 2026 season. An innings that finishes with wickets still in hand is not automatically a batting collapse. Likewise, a small winning chase may reflect a tiny target rather than poor batting. Keeping those cases separate makes the record easier to understand.

Lowest completed all-out innings between Mumbai Indians and Sunrisers Hyderabad, through IPL 2026
RankTeamTotalOversDateResult
1MI87 all out18.524 Apr 2018SRH won by 31 runs
2MI92 all out16.38 May 2016SRH won by 85 runs
3SRH96 all out17.46 Apr 2019MI won by 40 runs
4SRH113 all out20.017 May 2015MI won by 9 wickets
5SRH118 all out18.424 Apr 2018SRH won by 31 runs

Two of the five entries came from the same evening: 24 April 2018. Hyderabad were dismissed for 118, then bowled Mumbai out for 87. The winning side therefore appears on this list too. It is a reminder that a low total is a description of an innings, not proof that the team lost the match.

2018 at Wankhede: How Mumbai Indians Collapsed for 87

2018 at Wankhede: How Mumbai Indians Collapsed for 87

Mumbai looked well placed when the first innings ended. They had dismissed Hyderabad for 118 in 18.4 overs and needed 119 to win at home. That target required less than six runs an over across a full T20 innings. Instead, three early wickets took away the easy chase that Mumbai expected. The ball did not have to disappear to the boundary every over; they simply needed partnerships and patience.

Suryakumar Yadav was the one batter who stayed for a meaningful period. His 34 from 38 balls held the innings together while others fell around him. Krunal Pandya added 24, and their fourth-wicket stand of 40 briefly steadied the chase. The important turn came when Rashid Khan trapped Krunal leg before wicket. Mumbai then lost their remaining six wickets for just 26 runs and were all out for 87 in 18.5 overs.

Rashid Khan and Siddarth Kaul turned a small target into pressure

Rashid delivered four overs for only 11 runs and took two wickets, including a maiden over late in the chase. Siddarth Kaul took 3/23, while Basil Thampi returned 2/4. Sandeep Sharma set the tone with an economical new-ball spell. Those different roles mattered together: early pressure restricted scoring, spin blocked the middle overs, and the seamers finished the innings.

Mumbai’s 87 was not merely their lowest score against Hyderabad; it equalled their lowest IPL total at the time. The official match account also shows why this defeat was unusual: both teams were all out, yet the team defending 118 won comfortably. The IPL’s official report of the 2018 Wankhede match describes how the chase unravelled despite its modest target.

The lesson goes beyond one poor batting night. A team that starts chasing carefully can still lose control if dots accumulate, wickets interrupt the next partnership and a spinner is allowed to bowl at a batter under pressure. Hyderabad understood that a low total gave them little room to relax, so every dot ball was treated as a chance to create another mistake.

Mumbai’s 92 in 2016: When the New Ball Ended the Chase

Two years before the Wankhede upset, Hyderabad had already shown they could take Mumbai apart with disciplined pace bowling. On 8 May 2016 in Visakhapatnam, SRH posted 177/3. Shikhar Dhawan carried his bat for an unbeaten 82, while David Warner made 48. Mumbai needed a demanding but achievable 178, yet their innings broke almost as soon as it began.

The chase started with Parthiv Patel falling in the first over. Ashish Nehra then removed captain Rohit Sharma, Ambati Rayudu and Jos Buttler. Mumbai were 30/5 in the fifth over, so the side had lost half its wickets long before the end of the powerplay. That is the key reason the final total was only 92: the top order left too much work for batters who were supposed to support a finish, not rebuild an entire innings.

Nehra’s 3/15 and Mustafizur’s 3/16

Nehra took 3/15 from three overs, using swing, length and bounce rather than relying only on raw speed. Mustafizur Rahman later returned 3/16, while Barinder Sran took 2/18. Mumbai were dismissed in 16.3 overs and lost by 85 runs. Harbhajan Singh’s unbeaten 21 was their highest individual score. A chase that needed almost nine runs per over never developed a real platform.

This match differs from 2018 in one essential way. In 2016, Mumbai were chasing a strong score and were forced to recover while keeping up with the required rate. In 2018, they were chasing a small total but still could not protect their wickets. The two collapses show that batting failure can happen under very different forms of pressure.

SRH’s 96 in 2019: Alzarri Joseph’s Record-Breaking Spell

SRH's 96 in 2019: Alzarri Joseph's Record-Breaking Spell

Hyderabad’s lowest score against Mumbai came on 6 April 2019. MI had reached only 136/7, a total that initially seemed vulnerable at the Rajiv Gandhi International Stadium. Kieron Pollard changed the innings late with an unbeaten 46 from 26 deliveries. His four sixes helped Mumbai collect 56 runs in the final four overs and gave their bowlers something to defend.

SRH needed 137, but Mumbai’s debutant Alzarri Joseph immediately changed the rhythm of the match. His first ball dismissed David Warner. Instead of losing control after that start, Joseph repeatedly attacked the stumps and forced batters to commit to difficult shots. He finished with 6/12, then the best bowling figures in IPL history, while Hyderabad ended at 96 all out in 17.4 overs.

Rahul Chahar supported him with 2/21. Mumbai won by 40 runs despite scoring only 136 themselves. The contrast is striking: Pollard was the only batter in the entire match to reach more than 20, yet the side that found one late batting contribution and one extraordinary bowling spell won with room to spare.

Why 96 was more than a bad scorecard

The first wicket exposed Hyderabad early, but the decisive problem was that no long partnership followed. When a chase requires fewer than seven runs an over, batters should be able to leave risky balls and build the innings. Losing wickets forces the new player to start again, often against a bowler who already knows the conditions. Joseph kept taking those reset opportunities away from SRH.

There is an important distinction here between the lowest score in this fixture and the lowest total in the entire IPL. The first record belongs to MI’s 87 against SRH. The second involves matches across every franchise and cannot be answered from a head-to-head table alone. Similarly, Hyderabad’s 96 was its lowest IPL innings in 2019, but that franchise-wide mark has changed since then.

SRH’s 113 in 2015 and 118 in 2018: Two Very Different Outcomes

SRH's 113 in 2015 and 118 in 2018: Two Very Different Outcomes

On 17 May 2015 in Hyderabad, Sunrisers were bowled out for 113 in exactly 20 overs. This was a pressure match for the playoff race, and Mumbai’s opening bowlers removed both dangerous left-handed openers early. Lasith Malinga bowled Shikhar Dhawan, and Mitchell McClenaghan dismissed David Warner. Hyderabad were 7/2, an early hole that the middle order never fully repaired.

KL Rahul made 25, but MI kept taking wickets. McClenaghan finished with 3/16 and Malinga returned 2/17. The final pair stretched SRH to 113, with Dale Steyn contributing 19, but that was not enough. Mumbai chased the target by nine wickets. Here the low score led to the expected result: an easy win for the team with the much stronger bowling performance.

The 2018 meeting turned that story upside down. Hyderabad scored 118, only five runs more than its 2015 effort, yet defended it by 31 runs at Wankhede. Kane Williamson and Yusuf Pathan each scored 29 in the first innings. Mumbai’s bowlers had done most of their job; the batting side simply could not finish it. In a rivalry of wild score swings, those two nights show why the first-innings number needs the second-innings context.

How Batting Collapses Develop: Powerplays, Partnerships and Dot Balls

A collapse is not just a low final total. It is often a sudden run of wickets that stops a batting side from using the full innings. Mumbai’s 30/5 in 2016 was a powerplay disaster; SRH’s 7/2 in 2015 was the first warning; the 2018 MI chase began badly, recovered briefly, then lost six wickets for 26. The moment of maximum damage differed, but the pattern was familiar.

Fast bowlers create the first problem by moving the new ball or forcing rushed shots. When the top order is gone, middle-order players must decide whether to counterattack or absorb pressure. If several dots arrive together, the temptation to play a high-risk stroke increases. A wicket then brings a fresh batter into the same difficult situation. A low-scoring innings can snowball within two or three overs.

This is the other side of the MI VS SRH highest score story. In high-scoring matches, set batters can keep finding boundaries; in a collapse, every wicket brings a new player into a hard situation. The score alone never explains which team managed the pressure better.

Selected turning points in MI–SRH batting collapses
Match and inningsCollapse markerMain consequence
MI vs SRH · 2016MI 30/5 in the fifth overChase of 178 never settled
SRH vs MI · 2015SRH 7/2 earlyTop-order rebuild failed
MI vs SRH · 2018MI lost last six for 26119-run target went unchased
SRH vs MI · 2019Joseph took 6/12SRH all out for 96
SRH vs MI · 2025SRH 35/5 earlyRecovery reached only 143/8

The lesson is not that every side must attack harder. Against an accurate bowler, the safer option may be to rotate the strike and make the next partnership last six or seven overs. Once two batters settle, a chase can regain shape. Without that stand, even a small target becomes stressful, as Mumbai discovered in 2018.

Individual innings also change how these matches are remembered. Suryakumar Yadav’s 34 in the 87-run collapse was modest, yet it mattered more than a flashy cameo would have because nobody else could stay. When comparing those contributions with the MI VS SRH highest individual score, context is essential. A century in a 240-plus total and a patient 34 in an 87 all-out innings tell very different stories.

The 2025 Hyderabad Collapse: Why 143/8 Still Matters

Not every difficult MI–SRH innings ends with all ten wickets lost. On 23 April 2025, Hyderabad fell to 35/5 against Mumbai after a disastrous start. Trent Boult removed Travis Head and Abhishek Sharma, while Deepak Chahar also struck early. The top order had almost disappeared before Hyderabad could build momentum. At that stage, a score close to 100 looked possible.

Heinrich Klaasen changed the direction of the innings with 71 from 44 balls. Abhinav Manohar supported him with 43 from 37, and SRH reached 143/8 in 20 overs. Boult finished with 4/26, a reminder that a collapse and recovery can sit inside the same scorecard. Hyderabad avoided an all-out innings, but the damage to their scoring options had already been done.

Rohit Sharma made 70 from 46 balls as Mumbai reached 146/3 in 15.4 overs and won by seven wickets. The game belongs in a discussion of collapses, not in a ranking of the five smallest all-out totals. Treating 143/8 as though it were the same kind of record as 87 all out would hide an important difference: Klaasen and Manohar repaired the score, even though they could not make it a winning one.

IPL enthusiasts looking for more cricket-related information can explore an Online Cricket ID and learn about the features and terms offered by online platforms.

What the Lowest Scores Reveal About the MI–SRH Rivalry

The figures show that this contest cannot be explained by one permanent batting or bowling pattern. Mumbai suffered two of the three smallest totals, including a failed chase of 119. Hyderabad suffered the other three entries in the five-lowest list, including a 96-run chase against Joseph. The identity of the losing team changes, but the key driver does not: accurate bowling works best when wickets arrive before a stable partnership forms.

It is also risky to compare totals without reading the match situation. SRH’s 118 in 2018 was a winning score. Its 113 in 2015 was not. Mumbai’s 136/7 in 2019 was enough because Joseph delivered an extraordinary spell. A team scoring 143/8 in 2025 did better on paper than those earlier sides, yet still lost with more than four overs remaining. The same batting total can mean different things depending on the chase.

Meanwhile, the later high-scoring meetings show that modern attacking roles, conditions and batting depth can produce a completely different type of game. SRH made 277/3 in March 2024 and MI replied with 246/5. In April 2026, MI posted 243/5 and SRH chased 249/4. Those examples are useful comparisons, but they do not erase the low-score history. The rivalry contains both extremes, and the bowling side can still decide which direction a match takes.

Frequently Asked Questions

What is the lowest MI vs SRH score in IPL history?

Mumbai Indians’ 87 all out in 18.5 overs on 24 April 2018 is the lowest team total in MI–SRH IPL meetings through 2026. Sunrisers defended 118 and won by 31 runs.

What is Sunrisers Hyderabad’s lowest score against MI?

SRH were bowled out for 96 in 17.4 overs on 6 April 2019 in Hyderabad. Mumbai won by 40 runs after making 136/7.

When did Mumbai Indians score 92 against SRH?

MI made 92 all out in 16.3 overs at Visakhapatnam on 8 May 2016. SRH had scored 177/3 and won by 85 runs.

Which bowler caused SRH’s 96-run collapse in 2019?

Alzarri Joseph took 6/12 on his Mumbai Indians debut, the record IPL bowling spell at the time. Rahul Chahar supported him with 2/21.

Did SRH ever win after scoring only 118 against Mumbai?

Yes. SRH made 118 all out at Wankhede in 2018, then dismissed MI for 87. Hyderabad won by 31 runs despite its low first-innings score.

Was SRH’s 143/8 in 2025 an all-out collapse?

No. SRH fell to 35/5 but recovered to 143/8, thanks mainly to Heinrich Klaasen’s 71 and Abhinav Manohar’s 43. It was a difficult innings, not an all-out total.

Final Word: Low Totals Tell a Bigger Story

The mi vs srh lowest score remains Mumbai’s 87 in 2018, followed by their 92 in 2016 and Hyderabad’s 96 in 2019. Those numbers are memorable, but the reasons behind them matter more: early wickets, long periods without boundaries and bowling spells that kept new batters under pressure.

The most unusual result remains Hyderabad defending 118 at Wankhede. It proves that a team can win even after a batting failure if its bowlers respond better. Reading the score alongside the match situation gives a clearer picture of the rivalry than looking at the number by itself.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top