Last Updated: June 10, 2026
Quick Answer: Rajasthan Royals vs Mumbai Indians Match Scorecard of IPL 2026, Rajasthan Royals (RR) defeated Mumbai Indians (MI) by 27 runs in a rain-shortened 11-over match. RR posted a commanding 150/3, thanks to a sensational 77 off 32 balls* from Yashasvi Jaiswal and a rapid 39 off 14 balls from Vaibhav Sooryavanshi. In response, MI managed only 123/9 in 11 overs despite late efforts from Sherfane Rutherford and Naman Dhir.
Disclaimer: This article is based on official scorecard data from Cricbuzz and IPL 2026 records. Statistics and scores mentioned are accurate as per the official sources at the time of publication. While we strive for accuracy, cricket statistics can sometimes vary based on interpretation or official corrections. Always verify critical information with official IPL sources.
What Happened? The Match That Broke the Internet
When you hear Rajasthan Royals vs Mumbai Indians Match Scorecard, you need to understand one thing first: this wasn’t your typical cricket match. Rain had other plans. What was supposed to be a full 20-over game got trimmed down to just 11 overs per side—and honestly? That’s when Rajasthan Royals showed their true mettle.
Let me give you the headline: Rajasthan Royals vs Mumbai Indians Match Scorecard reads RR 150-3 (11 overs) defeating MI 123-9 (11 overs) by 27 runs. That 27-run margin? That’s massive in an 11-over contest. That’s not just winning; that’s dominating.
Breaking Down the Rajasthan Royals vs Mumbai Indians Match Scorecard
Alright, let’s talk numbers. When you look at the Rajasthan Royals vs Mumbai Indians Match Scorecard, the first thing that jumps out is how aggressive Rajasthan got right from ball one.
Rajasthan Royals’ Batting Performance
Here’s what the opening showed us: Yashasvi Jaiswal walked out, and honestly, it felt like watching a video game on easy mode. The man put up 77 runs without getting out—not out at stumps. In just 32 balls. That’s a strike rate of 240.62. Do you know what that means? Almost two-and-a-half runs per ball. Every single ball was either a boundary or aggressively taken.
Then came Vaibhav Sooryavanshi. This guy came in and said, “Hold my cola.” 39 runs off just 14 balls. A strike rate of 278.57. These two were absolutely relentless.
Here’s the complete RR batting breakdown:
| Batter | Dismissal | Runs | Balls | Fours | Sixes | Strike Rate |
|---|---|---|---|---|---|---|
| Yashasvi Jaiswal | Not Out | 77 | 32 | 10 | 4 | 240.62 |
| Vaibhav Sooryavanshi | c Tilak Varma b Shardul Thakur | 39 | 14 | 1 | 5 | 278.57 |
| Dhruv Jurel (wk) | lbw b AM Ghazanfar | 2 | 3 | 0 | 0 | 66.67 |
| Riyan Parag (c) | c Tilak Varma b AM Ghazanfar | 20 | 10 | 1 | 2 | 200.00 |
| Shimron Hetmyer | Not Out | 6 | 7 | 0 | 0 | 85.71 |
| Extras | – | 6 | – | – | – | – |
| TOTAL | 150-3 | 150 | 11 Overs | 12 | 11 | 13.64 RR |
Did you notice something? They hit 11 sixes in just 11 overs. That’s one six per over. In an 11-over game, that’s absolutely mental. The Rajasthan Royals vs Mumbai Indians Match Scorecard tells a story of pure carnage.
How Much Did Each Bowler Get Hit in Rajasthan Royals vs Mumbai Indians Match?
Let me break down who suffered the most in this Rajasthan Royals vs Mumbai Indians Match Scorecard:
| Bowler | Overs | Maidens | Runs | Wickets | Wides | Economy |
|---|---|---|---|---|---|---|
| Deepak Chahar | 1 | 0 | 22 | 0 | 0 | 22.00 |
| Jasprit Bumrah | 3 | 0 | 32 | 0 | 1 | 10.70 |
| Trent Boult | 1 | 0 | 22 | 0 | 1 | 22.00 |
| Hardik Pandya (c) | 2 | 0 | 17 | 0 | 0 | 8.50 |
| Shardul Thakur | 2 | 0 | 36 | 1 | 3 | 18.00 |
| AM Ghazanfar | 2 | 0 | 21 | 2 | 1 | 10.50 |
Look at those economy rates. Deepak Chahar? 22.00. Trent Boult? 22.00. These are world-class bowlers getting absolutely hammered. Shardul Thakur’s 36 runs off 2 overs tells you everything about how Rajasthan Royals vs Mumbai Indians Match Scorecard unfolded.
Mumbai Indians’ Response: When Good Batting Still Isn’t Enough
Now, here’s the thing about MI. They’re not a team that crumbles easily. But sometimes, you need 180+ to compete when your opposition has put 150 in 11 overs. They scored 123. That’s where the 27-run gap came from.
Let me show you who did what for Mumbai:
Mumbai Indians’ Batting in the Rajasthan Royals vs Mumbai Indians Match Scorecard:
| Batter | Dismissal | Runs | Balls | Fours | Sixes | Strike Rate |
|---|---|---|---|---|---|---|
| Ryan Rickelton (wk) | c Dhruv Jurel b Jofra Archer | 8 | 4 | 0 | 1 | 200.00 |
| Rohit Sharma | lbw b Sandeep Sharma | 5 | 6 | 0 | 0 | 83.33 |
| Suryakumar Yadav | c Jofra Archer b Nandre Burger | 6 | 3 | 0 | 1 | 200.00 |
| Tilak Varma | c Shimron Hetmyer b Ravi Bishnoi | 14 | 10 | 2 | 0 | 140.00 |
| Hardik Pandya (c) | c Yashasvi Jaiswal b Ravi Bishnoi | 9 | 6 | 2 | 0 | 150.00 |
| Naman Dhir | c Ravi Bishnoi b Nandre Burger | 25 | 13 | 3 | 1 | 192.31 |
| Sherfane Rutherford | c Sandeep Sharma b Tushar Deshpande | 25 | 8 | 2 | 2 | 312.50 |
| Shardul Thakur | c Dhruv Jurel b Sandeep Sharma | 8 | 7 | 1 | 0 | 114.29 |
| Deepak Chahar | Not Out | 6 | 5 | 1 | 0 | 120.00 |
| Trent Boult | run out (Jofra Archer) | 1 | 2 | 0 | 0 | 50.00 |
| Jasprit Bumrah | Not Out | 5 | 2 | 1 | 0 | 250.00 |
| Extras | – | 11 | – | – | – | – |
| TOTAL | 123-9 | 123 | 11 Overs | 12 | 5 | 11.18 RR |
Now here’s something interesting. Sherfane Rutherford hit a blistering 25 off just 8 balls. Naman Dhir got 25 off 13. These were decent contributions, but they came too late and weren’t quite enough. The Rajasthan Royals vs Mumbai Indians Match Scorecard shows that MI kept losing wickets at regular intervals.
The Bowling Battle That Won the Rajasthan Royals vs Mumbai Indians Match
When you’re defending 150 in 11 overs, bowling matters. A lot. Let me show you who the real heroes were:
Rajasthan Royals’ Bowling Attack:
- Jofra Archer: 2 overs, 17 runs, 1 wicket (economy: 8.50)
- Nandre Burger: 2 overs, 21 runs, 2 wickets (economy: 10.50)
- Sandeep Sharma: 3 overs, 26 runs, 2 wickets (economy: 8.70)
- Tushar Deshpande: 2 overs, 29 runs, 1 wicket (economy: 14.50)
- Ravi Bishnoi: 2 overs, 25 runs, 2 wickets (economy: 12.50)
Notice that Ravi Bishnoi and Nandre Burger each took 2 wickets? In an 11-over game, that’s significant. The Rajasthan Royals vs Mumbai Indians Match Scorecard wouldn’t have read the way it did without these two.
Expert Analysis: Why RR Won This Rajasthan Royals vs Mumbai Indians Match
Let me break it down simply:
1. Aggressive Batting from Ball One Yashasvi Jaiswal didn’t come to survive; he came to thrive. When you’re in an 11-over game, time is your enemy. RR understood that. They went for every ball, and their strike rates (240.62, 278.57) prove it.
2. Early Momentum in the Powerplay The powerplay (overs 1-3.2) brought 59 runs for RR. That’s almost 40% of their total runs in roughly 30% of their overs. MI’s powerplay? Just 30 runs. That swing right there decided the Rajasthan Royals vs Mumbai Indians Match Scorecard.
3. Effective Bowling Under Pressure When you’re defending 150 in 11 overs, you can’t bowl loose balls. RR’s bowlers had economy rates between 8.50 and 12.50 (except one outlier). That discipline was crucial.
4. Catching and Fielding MI lost too many batters to catches. The Rajasthan Royals vs Mumbai Indians Match Scorecard shows multiple catches, which suggests sharp fielding from RR.
Why This Rajasthan Royals vs Mumbai Indians Match Scorecard Matters
Listen, Rajasthan Royals vs Mumbai Indians Match performances like this matter because they show what’s possible when conditions are compressed. Rain-affected cricket brings out the aggressive sides of teams. RR showed they have that edge.
The Rajasthan Royals vs Mumbai Indians Match Scorecard will be remembered because:
- It’s a masterclass in aggressive batting in limited time
- It shows how quickly momentum can shift in T20 cricket
- It proves that Yashasvi Jaiswal is a generational talent
- It reminds us that not all matches go 20 overs, and adaptation is key
About RR vs MI Historical Context
When you talk about RR vs MI 2025 or RR vs MI 2024, they’re usually competitive matches. But in 2026, with these specific conditions and this specific Rajasthan Royals vs Mumbai Indians Match Scorecard, it was a performance that stood out.
