Mumbai Indians closed out their first away double of the season with a six-wicket win over Rajasthan Royals at the Sawai Mansingh Stadium on Monday night, chasing 207 with nine balls to spare. The result pushes them to 14 points from 11 games and keeps the top-two conversation open; Royals stay ninth with the same win count as the seventh-placed side but a net run rate that has now dipped to –0.518 after three straight losses.

For most of the night the contest looked like a Royals innings — until it didn't. Below covers the four passages that decided the match, the numbers behind each, and what they imply for the next week of fixtures. Our running IPL coverage, including squad moves and injury news from across the league, lives at the IPL news & analysis hub.

The powerplay that set the tone

Rajasthan came out batting first and reached 71 without loss in the first six overs — the highest powerplay score Royals have posted at home this season. Yashasvi Jaiswal took 14 off the second over of the innings off Trent Boult, all behind square, and Sanju Samson looked in control from the other end with three measured boundaries through the off side.

The reason that score still became chaseable was the second-half slowdown. MI's spinners — Karn Sharma and the part-time options — conceded only 6.1 runs per over across overs 11 to 16, dragging the projected total down from a mid-220s trajectory to the eventual 206/6. The dot percentage in that middle phase (47%) was the second-highest Royals have recorded in a losing cause all year.

The wicket that changed the chase

MI lost Rohit Sharma in the third over for 11, caught at deep square leg trying to hit across the line. They were 32 for 1 and the chase rate had nudged above 11. What followed was the single passage the highlights package tends to skip: a six-over consolidation in which Will Jacks and Suryakumar Yadav added 58 without taking meaningful risk, lifting the required rate from 11.2 to 10.4 without losing a wicket.

“The chase never felt in trouble from that point, even when they took a wicket. We had wickets in hand and the asking rate was inside ten. That's the situation you want going into the last five overs at the Sawai Mansingh.” — Stand-in MI batter, post-match

The 19th over that finished it

Avesh Khan's 19th over went for 22. Jacks took 14 off the first four balls — three boundaries and a pulled two — and Suryakumar finished the over with a slog-swept six off a full toss that dipped below the shin line. The required equation at the start of that over had been 27 off 12; by the end it was 5 off 6.

What made the over winnable rather than merely manageable was the match-up. Khan had been Royals' most economical death bowler in the previous four games (economy 8.1 in overs 18–20), and the Royals captain kept him on for a fourth consecutive death over rather than going back to the part-time left-arm spinner who'd taken Jacks earlier in the innings. In hindsight, the change would have been the right one. By the time Avesh came off, the chase was effectively over.

Where the Royals lost the script

Three patterns from Royals' last three games are now visible in the data:

None of those numbers is fatal in isolation. Taken together they describe a side whose ceiling on its day is still 200-plus, but whose floor is now visibly lower than it was six weeks ago. The fixture list is not kind either: Royals face three of the top four in their next four matches.

What MI take from the night

Beyond the two points, the chase validated two of the conversations the MI think-tank have been having all week. First, the decision to hold Jacks back at No. 3 rather than opening — a structural choice that has divided opinion in the Mumbai press — looks like the right one when the chase is 207-plus: it gives the innings a left-right combination through the middle and stops Rohit from facing the new ball on surfaces where the ball moves early. Second, Hardik Pandya bowling his full four overs in the first innings, rather than holding back for the death, gave the side a wicket-taking option in overs 11–14 that Royals could not neutralise.

By the numbers

What to watch next

Mumbai host Lucknow Super Giants on Thursday — the side that took them apart in the reverse fixture three weeks ago, and a useful benchmark for whether this chase was a turn of form or a one-off. Royals travel to Hyderabad on Wednesday to face Sunrisers, with question marks over whether the management will rotate the seam attack after Avesh's final-over punishment.

Updated 22:48 IST with post-match quotes and the innings-phase split.