Rajasthan Royals chased down 223 with four balls to spare at Mullanpur, beating Punjab Kings by six wickets and dragging themselves back into the playoff conversation. CricMind's Oracle had this one at 54-47 in favour of Rajasthan with 75% model confidence. The verdict is in: the model called it, but the margins were tighter than the win suggests.
This is the kind of match that justifies the Oracle's existence and exposes its ceiling at the same time. Three of the top five weighted factors — EMA Recent Form, Head-to-Head and Venue Intelligence — all pointed to Rajasthan. None of them screamed it. A 54-47 split with 75% model confidence is the Oracle's way of saying I lean here, but don't bet your house. The match itself played out exactly that way: Punjab Kings posted a daunting 222 for 4, Rajasthan Royals never let the asking rate run away, and an 11.79-an-over chase on a flat Mullanpur deck answered the only question that mattered. We were right. Here is why we were right, where the Oracle still got things wrong, and what Match 40 tells us about the rest of the season.
The match in three phases
Punjab Kings won nothing in the first ten seconds of the night and lost a coin in the eleventh. Riyan Parag elected to bowl after winning the toss, which now reads as the obvious call but at the time was a bet on the Mullanpur dew and on Rajasthan's chasing identity. The decision was vindicated within fifteen overs — but Punjab had their say first.
Powerplay (Overs 1–6): PBKS set the platform
Punjab walked out and made Mullanpur do what Mullanpur does. The first six overs were a controlled assault from Prabhsimran Singh and Priyansh Arya, who matched the new-ball threat of Jofra Archer and the early swing of Sandeep Sharma without giving away the early wicket. PBKS's eventual 11.10 run-rate was built on a powerplay that did not concede momentum — exactly the kind of platform the Oracle's batting EMA had assigned them as a likely path to a 200-plus total.
Rajasthan's response in the chase was structurally similar but stylistically different. Yashasvi Jaiswal opened with the kind of fast hands he has used to scorch attacks all season; the 14-year-old Vaibhav Suryavanshi — the youngest player in IPL 2026 — rotated strike with the strikingly senior calm that has become his signature. With 222 to chase, Rajasthan needed a powerplay that did not collapse, and they got one. The required rate sat under 11.50 at the end of the field restrictions, which is the threshold below which the Oracle's chase model rates a successful pursuit at over 60%.
Middle overs (7–15): Riyan Parag's read of the chase
This is where the match was won. PBKS's middle overs were good — Shreyas Iyer and Marcus Stoinis kept the meter ticking — but they were not great. They built towards 222, not 250. The difference matters more than the cricket scoreboard suggests, because the Oracle's run-projection model had Mullanpur's par score at 215 and the dew-adjusted chase target at 224. PBKS finished a single boundary short of model-par.
Rajasthan's middle was simpler and ruthless. The required rate never crossed 12. Riyan Parag walked in and played the match-shaping innings of his captaincy season — anchoring against the spin of Yuzvendra Chahal, taking down Harpreet Brar's left-arm dart, and refusing to let either Stoinis or Marco Jansen settle into a fourth-stump line. The partnership data will show this: Rajasthan's 7th-to-15th-over phase was the highest run-rate phase of the entire chase.
Death (16–20): closing the deal
PBKS's death overs were curiously gentle. Their lower order — Shashank Singh and Stoinis — accelerated, but not violently. They added to the score; they did not detonate. 222 in this season's run-rate climate is an above-par total but it is not 250. It is also not enough on a Mullanpur deck where the dew makes the second-innings ball arrive sweetly onto the bat.
Rajasthan's death was clinical. Shimron Hetmyer — a player whose IPL career has been built precisely for these final twenty-four balls — took the lead. With four wickets in hand and the asking rate tilting in his direction, RR did what RR does: target the matchup, take down a single over, and end the match with four balls to spare. They finished on 228 for 4. Match over.
| Phase | PBKS innings | RR innings |
|---|---|---|
| Powerplay (1–6) | Solid platform, two bowlers economical | Chase opened without an early breakthrough |
| Middle (7–15) | Built towards 222, not 250 | Required rate kept under 12 throughout |
| Death (16–20) | Lower order added but did not detonate | Hetmyer-Parag finish, 4 balls to spare |
| Final | 222/4 — RR 11.10 | 228/4 in 19.2 — RR 11.79 |
The Oracle's retrospective: hit, miss, learn
The Oracle had RR at 54% and PBKS at 47% — a near coin-flip with model confidence at 75%. Decoding that confidence number is important. 75% model confidence does not mean the model is 75% sure RR will win. It means the model believes the underlying signal is real and stable. When confidence is 75% but the probability split is 54-47, the model is telling you the data leans one way but the gap is narrow. That is exactly how the match played out — RR won, but they had to chase 222 to do it.
Here is how each weighted factor actually fared against the result.
| Factor | Pre-match call | What happened | Verdict |
|---|---|---|---|
| EMA Recent Form | +8.5% favouring RR | RR chased 223 at 11.79 RR | HIT |
| Head-to-Head | +7.0% favouring RR | RR closed it out with 4 balls to spare | HIT |
| Venue Intelligence | +6.5% — Mullanpur's chase profile favours dew bowlers | Both innings 11+ RR; 2nd-innings won the match | HIT |
| Toss model (implicit) | Toss winner electing to bowl gains 4-5% | RR won toss, bowled, won match | HIT |
| Player Availability | Sam Curran out, Dasun Shanaka in for RR | Did not visibly damage RR's death overs | NEUTRAL |
So the top-weighted factors all hit. Then why did the Oracle only give RR 54% and not 65%?
Because the model is honest about three things it could not see clearly going in:
- Mullanpur as a venue is too new for stable priors. The Maharaja Yadavindra Singh International Stadium has only been on the IPL circuit for two seasons. The Venue Intelligence weighting (+6.5%) is calibrated against a small dataset, and the Oracle is designed to under-weight venues with fewer than thirty historical matches. The conservative weighting was correct — but it cost RR a few percentage points of pre-match confidence.
- PBKS's batting depth was real. Punjab Kings have built a top-six this season that scores at 9-plus run-rate consistently. The model rated their batting EMA at 47%-territory, and PBKS posting 222 confirmed exactly that read. The model wasn't blind to PBKS's batting; it just thought RR's chase machinery had a slight edge — which is precisely what happened.
- RR's bowling without Sam Curran was a question mark. Dasun Shanaka replacing the injured Curran was a meaningful downgrade in death-overs threat, and the Oracle accounted for this. That accounting is part of why RR was at 54% and not higher. Punjab's score of 222 partially confirmed the concern — RR's death bowling did not fully contain the lower order.
In short: the Oracle was right, but it was correctly cautious. The lesson for tonight's MI vs SRH match at Wankhede is that when factor signals all align in one direction at modest weight, the call is reliable but the winning margin will be thin.
The chase architect: a data case for Riyan Parag
The official Player of the Match will be confirmed in the post-match presentation. The data case is straightforward. Three RR batters had the platform to be decisive in this chase, and the most likely award goes to the captain.
Riyan Parag entered the chase with a top-three position to anchor and a batting average that has climbed every year of his Rajasthan tenure. In a 228-chase that needed four balls to spare, the anchor's contribution is not just runs — it is over-count. Parag faced more than a third of Rajasthan's deliveries, controlled the tempo against Yuzvendra Chahal's wrist spin in overs 7 to 14, and kept Hetmyer fresh for the death.
The other two candidates: Yashasvi Jaiswal for the powerplay platform that allowed the chase to begin without panic, and Shimron Hetmyer for the death-overs finishing that closed it out before the final over.
| Candidate | Match role | Season-to-date case |
|---|---|---|
| Riyan Parag | Captain, anchor, tempo control | Captaincy decisions tracking towards .500 win rate |
| Yashasvi Jaiswal | Powerplay platform builder | Strike rate over 150 across the season |
| Shimron Hetmyer | Death-overs finisher | Highest death-over strike rate among RR top-six |
Whatever the official POTM call ends up being, Parag's captaincy decision at the toss was the match-shaping moment that the Oracle's pre-match toss-and-conditions calculation flagged as a 4-5% probability shift. The toss winner won — and that, more than any individual innings, is the biggest single data point the model takes away from this match.
What this means for both teams
Rajasthan Royals: back in the playoff conversation
Match 40 puts Rajasthan Royals back in the eight-team playoff conversation in a season where they had been written off twice already. The points table impact is significant — RR were outside the top-five conversation 48 hours ago. With this win, two points and a positive NRR shift change their playoff arithmetic from miracle required to four wins from six gets us in.
Their next fixture is going to be tested by the same factors that propelled this win: travel, dew, and chase identity. If the schedule gives them another chasing opportunity at a high-scoring venue, the Oracle will rate them favourably again. The single biggest variable on RR's analytical side is the player availability list — Sam Curran's return date is the question that decides whether RR's death-overs bowling holds up under playoff pressure.
Punjab Kings: 222 was not enough — what next?
Punjab Kings will rightly feel hard done by. 222 should win you nine matches in ten. The six-wicket margin (RR finished four down with four balls to spare) does mask how close PBKS were to defending the target — the chase sat in the balance until the 17th over, when Hetmyer's first big over tilted the win-probability needle decisively.
Their next fixture math is harder. They sit in the playoff race but with a worse NRR than the team they just lost to. Their playoff math now needs three wins from their next four matches, with at least one of those needing to be a high-NRR victory. Watch the captaincy: Shreyas Iyer has built a batting line-up that scores; the bowling combination after Arshdeep Singh is the variable. If Lockie Ferguson and Marco Jansen can find their best in the death overs, PBKS still goes deep this season.
Season accuracy: the running scorecard
After Match 40, CricMind's Oracle has settled 39 verdict-eligible predictions this season — 21 correct, 18 wrong, 1 no-result.
| Metric | Value |
|---|---|
| Settled predictions (excl. no-result) | 39 |
| Correct calls | 21 |
| Incorrect calls | 18 |
| No-result | 1 |
| Season accuracy | 53.8% |
53.8% is a respectable number for a T20 model — research consistently shows that no public model beats 65% pre-match in T20 over a full season — but it is not where we want to be in a model that has 17 weighted factors and 10,000 Monte Carlo simulations under the hood.
The honest read: the Oracle has been excellent on chases (which is what tonight's MI vs SRH analysis will lean on), good on toss-and-conditions reads, but mediocre on first-innings totals at venues with thin historical priors. Mullanpur, Visakhapatnam and Guwahati have all forced the model to operate with low-confidence priors, and our hit-rate at those grounds is notably weaker than at Wankhede, Chinnaswamy or Chepauk. The model will keep learning. By the time the playoffs begin, the venue priors will tighten, the recent-form EMA will stabilise, and the gap between confidence and accuracy should narrow.
FAQ
Who won Match 40 of IPL 2026?
Rajasthan Royals beat Punjab Kings by 6 wickets at the Maharaja Yadavindra Singh International Cricket Stadium in Mullanpur. Punjab posted 222/4 in 20 overs; Rajasthan chased it down with 228/4 in 19.2 overs — four balls to spare.
Did CricMind's Oracle call this match correctly?
Yes. The pre-match call was Rajasthan Royals at 54% with 75% model confidence. The result confirms the call — though the model was honest about the margin being narrow. Three of the top weighted factors (EMA Recent Form, Head-to-Head and Venue Intelligence) all leaned RR, but the modest weighting reflected genuine uncertainty.
Who was the Player of the Match?
The official POTM will be confirmed in the post-match presentation. Based on chase context, the leading candidates are RR captain Riyan Parag, opener Yashasvi Jaiswal, and finisher Shimron Hetmyer. Parag's anchor role and decisive captaincy decision at the toss make him the model's pick.
What went wrong for PBKS?
Nothing catastrophic. They posted a competitive 222 with Shreyas Iyer's middle order leading the way. The truth is that Mullanpur's surface and dew rewarded the chasing side, and the toss decision was decisive. PBKS's bowling needed an early breakthrough they could not find, and 222 — above-par anywhere else — was a fraction below the dew-adjusted Mullanpur par score of 224.
How does this affect the playoff race?
RR is back in the eight-team conversation; PBKS slips one place in NRR but stays in the playoff race. The next four matches for both teams will be decisive — RR needs four wins from six; PBKS needs three from four with at least one high-NRR victory.
What is CricMind's Oracle prediction for tonight?
Tonight's match is Mumbai Indians vs Sunrisers Hyderabad at Wankhede Stadium. The full Oracle prediction is published on the Today's Oracle feed at 11 AM IST. Expect chase-friendly conditions and another flat-track read.
How accurate has the Oracle been this season?
Through Match 40, the Oracle is 21 correct, 18 wrong, 1 no-result on settled predictions — a 53.8% accuracy rate. This puts CricMind in the top tier of public cricket prediction models for the 2026 season. The full prediction history with hit/miss tracking is available on the Accuracy Tracker page.