IPL 2026: Hardik Pandya laments 73 runs conceded in last 5 overs in MI's 30-run loss

Share:
Audio Loading voice…
IPL 2026: Hardik Pandya laments 73 runs conceded in last 5 overs in MI's 30-run loss

Synopsis

Mumbai Indians had Rajasthan Royals on the ropes at 119/5 — then conceded 73 in the last five overs. Jofra Archer's 32 off 15 balls turned the match, and his 3/17 with the ball sealed it. Hardik Pandya's side finished second-last with eight points from 14 games, making IPL 2026 one of the five-time champions' worst seasons on record.

Key Takeaways

Mumbai Indians lost to Rajasthan Royals by 30 runs in Match 69 of IPL 2026 at Wankhede Stadium on 24 May .
Rajasthan recovered from 119/5 to post 205/8 , with Jofra Archer smashing 32 off 15 balls including 3 sixes .
Archer also took 3/17 with the ball; Burger , Brijesh Sharma , and Yash Raj Punja each claimed 2 wickets .
Suryakumar Yadav top-scored for MI with 60 ; Will Jacks (33) and Pandya (32) also contributed.
MI ended the season in second-last place with 8 points from 14 matches .
Pandya attributed the defeat to conceding 73 runs in the last 5 overs and losing early wickets in the chase.

Hardik Pandya admitted that conceding 73 runs in the final five overs proved decisive as Mumbai Indians fell short by 30 runs against Rajasthan Royals in Match 69 of IPL 2026 at the Wankhede Stadium on Sunday, 24 May. The five-time champions were restricted to 195/9 in their chase of 205, ending their campaign in second-last place on the points table.

How Rajasthan Royals Escaped from 119/5

Mumbai Indians had the Royals firmly in their grip, dismissing the dangerous opening pair of Yashasvi Jaiswal and Vaibhav Sooryavanshi cheaply and reducing the visitors to a precarious 119/5. What followed, however, was a stunning lower-order assault. Jofra Archer delivered a brutal cameo of 32 off 15 balls, laced with three sixes, before Ravindra Jadeja (19* off 11) and Nandre Burger (10* off 3) kept the momentum going. Rajasthan ultimately posted a challenging 205/8 in 20 overs — a recovery that proved too costly for MI to overcome.

Mumbai Indians' Chase Falls Apart

In reply, Mumbai's innings never quite found its footing. Early wicket losses undermined the chase from the outset, and despite a fighting 60 by Suryakumar Yadav and useful contributions from Will Jacks (33) and Pandya himself (32), the target remained out of reach. Archer then turned match-winner with the ball too, finishing with 3 for 17 in a brilliant four-over spell. Nandre Burger (2/43), Brijesh Sharma (2/26), and Yash Raj Punja (2/44) each claimed two wickets as Rajasthan wrapped up the match.

What Pandya Said

The MI skipper was candid in his post-match assessment. 'We gave away 10-15 too many. It was chaseable, but we lost too many early wickets. Wicket played similarly in both innings; you had to hold your shape and hit good cricketing shots to get value,' Pandya said. He added that small margins made the difference: 'Last five overs are always difficult. If you can stop one/two boundaries, you can keep teams 12-15 runs short. Conceding 73 in the last five cost us too.' On his personal fitness after a hectic schedule post the T20 World Cup, Pandya was upbeat: 'Body's fine. I bat, bowl, field, and slip. It's fair to have a game where I just batted and enjoyed myself.'

MI's Forgettable IPL 2026 Campaign

The defeat sealed a disappointing season for Mumbai Indians, who ended with just eight points from 14 matches — finishing in second-last position in the 10-team standings. The five-time champions consistently failed to fire collectively with both bat and ball, and Sunday's collapse from a position of strength at 119/5 encapsulated the inconsistency that plagued them throughout the tournament. This marks one of MI's worst IPL campaigns in recent memory, raising questions about squad balance and death-bowling strategy heading into the next season.

Point of View

Jadeja, and Burger is not bad luck; it is a systemic failure of death-bowling execution. Pandya's candid admission about the last five overs is honest, but it sidesteps a deeper question: why does a franchise with MI's resources repeatedly lack the bowling depth to defend positions of strength? With eight points from 14 games, this campaign demands a structural rethink — not just a personnel reshuffle.
NationPress
7 Aug 2026

Frequently Asked Questions

Why did Mumbai Indians lose to Rajasthan Royals in IPL 2026 Match 69?
Mumbai Indians lost by 30 runs primarily because they conceded 73 runs in the last five overs, allowing Rajasthan to recover from 119/5 to post 205/8. In the chase, early wicket losses derailed MI's innings despite contributions from Suryakumar Yadav (60), Will Jacks (33), and Hardik Pandya (32).
Who turned the match for Rajasthan Royals from 119/5?
Jofra Archer played the decisive cameo, hitting 32 off 15 balls with three sixes to shift momentum. Ravindra Jadeja (19* off 11) and Nandre Burger (10* off 3) then pushed Rajasthan to 205/8, a total that proved beyond Mumbai's reach.
How did Jofra Archer perform with the ball?
Archer was equally influential with the ball, finishing with figures of 3 for 17 in four overs — a spell that effectively ended Mumbai's chase. Nandre Burger, Brijesh Sharma, and Yash Raj Punja each took two wickets to support him.
Where did Mumbai Indians finish in IPL 2026?
Mumbai Indians finished in second-last position in the 10-team standings, ending the season with eight points from 14 matches. It is widely regarded as one of the five-time champions' worst IPL campaigns in recent years.
What did Hardik Pandya say after the match?
Pandya acknowledged that giving away too many runs in the death overs was the turning point, saying 'Conceding 73 in the last five cost us too.' He also noted that losing early wickets hampered the chase, though he said his body was in good shape despite the hectic post-T20 World Cup schedule.
Nation Press
The Trail

Connected Dots

Tracing the thread behind this story — newest first.

8 Dots
  1. Latest 2 months ago
  2. 2 months ago
  3. 2 months ago
  4. 2 months ago
  5. 4 months ago
  6. 4 months ago
  7. 1 year ago
  8. 1 year ago
Google Prefer NP
On Google