[Gujarat Titans](/teams/gt) battered [Rajasthan Royals](/teams/rr) for 229/4 at Sawai Mansingh Stadium and then bowled the home side out for 152 inside 17 overs. The margin — 77 runs — was one of the most lopsided results of the IPL 2026 season so far. CricMind's Oracle had backed Rajasthan at 51% with a 74-point confidence reading the night before. The model missed. Honestly, it missed badly.
This is the post-mortem nobody else in cricket media writes — because it forces us to grade our own work. Below: the phase-by-phase story of how Shubman Gill's side dismantled the Royals at home, every Oracle factor laid bare against what actually happened, the data case for the player of the match, and the playoff math both sides walk into the back end of the season carrying.
The match — phase by phase
Riyan Parag called the toss correctly and chose to bowl. With dew expected at Jaipur and the Sawai Mansingh surface reading slow under lights, the call was textbook. It was also where the Oracle's confidence in Rajasthan was, in retrospect, quietly justified — the venue split has favoured the side bowling first in the majority of recent IPL matches at this ground. The toss didn't fail the model. The 40 overs that followed did.
| Phase | GT (1st innings) | RR (2nd innings) |
|---|---|---|
| Powerplay (1–6) | Aggressive launch, top order ahead of the rate | Lost early wickets, run-rate stalled |
| Middle (7–15) | Buttler-led acceleration, partnership-heavy | Required rate ballooned past 13 |
| Death (16–20) | Six-hit barrage, 76+ in the last five | Innings folded inside 17 overs |
| Final | 229/4 (RR 11.45) | 152 all out (RR 9.21) |
Powerplay — Gujarat front-foot from ball one
Gujarat's intent in the first six overs was unambiguous. With Jos Buttler opening alongside Shubman Gill, the pair targeted the new-ball pace from Jofra Archer and Sandeep Sharma in the air rather than along the ground. Rajasthan's seam attack, which has been one of the more economical powerplay units in IPL 2026, leaked at over ten runs per over for the first time in five matches. The 16 wides Gujarat eventually accumulated by the 20th over — a Rajasthan season-high — started here, with Archer's lengths drifting and the Royals' fielding loose at the ropes.
The first signal that the model had under-priced was the boundary distribution. Rajasthan's powerplay at home this season has averaged 38–42 — a competitive but not punishing band. Gujarat went past that ceiling inside the powerplay. Once a top-order pair gets ahead of the rate at this ground, defending the back end becomes a trial in damage limitation rather than dictation. That is exactly what happened.
Middle overs — Buttler vs his old employer
The 7-to-15 phase is where the match was won. Buttler, who returned to Jaipur for the first time as an opposition player after a decade with the Royals, batted with the kind of cold precision that prompted his off-season switch. Gill rotated strike alongside him, Sai Sudharsan walked in at the second drop and never let the rate dip below ten. Rajasthan's spin pair — Ravi Bishnoi and Ravindra Jadeja — were taken for combined figures that read like a pre-season warm-up game. Bishnoi, in particular, hasn't gone for nine an over at Sawai Mansingh in two seasons. He did tonight.
The middle-over scoring rate, in fact, is what made 230 inevitable. Most IPL totals north of 220 are built on a launch-pad opening stand and a death surge with the middle stagnating in between. Gujarat scored at 11+ throughout the middle phase. That is the partnership profile of a side that knew the surface and read it before Rajasthan did.
Death overs — the demolition
Gujarat closed at 229/4. The last five overs alone produced more than 76 runs and signalled the chase was already an outlier ask. Rajasthan's death-bowling has been a vulnerability the model under-weighted: in their last several outings, the Royals' 16-to-20 economy has crept north of eleven — a number that should have nudged Oracle's pre-match probability towards Gujarat by another four to five percentage points all on its own.
The reply was a procession. Yashasvi Jaiswal fell early to the new ball, the middle order never strung a partnership of consequence together, and the Royals lost their last six wickets for under 30 runs as the required rate climbed past 14. Kagiso Rabada and Mohammed Siraj extracted reverse swing under lights — exactly the conditions Rajasthan's lower order has historically struggled with. Rajasthan were bowled out in the 17th over chasing 230. The 77-run margin understates the gap.
The Oracle's retrospective — factor by factor
This is the section the Oracle gets graded on. Pre-match, the model gave Rajasthan 51% to Gujarat's 49%, with a confidence reading of 74. Three top factors drove that lean. All three pointed Rajasthan's way. None of the three played out as forecast.
| Factor | What we said pre-match | What actually happened | Verdict |
|---|---|---|---|
| EMA Recent Form (+11.2%) | RR trending positive — momentum favours home side | Form was overstated; bowling unit was carrying patchy batting | Miss |
| Head-to-Head (+6.0%) | RR historically edge GT, especially at home | Pattern broke — GT recorded one of their largest-ever wins over RR | Miss |
| Venue Intelligence (+5.3%) | Sawai Mansingh has favoured RR's match-up profile | Pitch played truer and higher-scoring than the rolling average | Miss |
| Squad availability | Both sides at full strength — neutral | Neutral, as expected | Hit |
| Toss leverage | Bowling first carries a slight edge | RR won toss + bowled — and lost anyway | Miss |
Five of the model's top inputs landed on the wrong side of the result. That is not a marginal miss — that is a structural one. Two readings deserve calling out specifically.
EMA Recent Form was over-weighted. Rajasthan's exponential moving average looked positive on paper because three of their recent wins came in low-scoring chases. The model treated those as evidence of a pattern. They were, in practice, evidence of a defensive ceiling — Rajasthan haven't had to bat on a 220+ surface this season, so the data didn't punish them for not being able to. When the pitch produced one, the side cracked.
Head-to-Head was stale. The +6% RR lean came from career-long IPL meetings between the two franchises, including matches where Gujarat's current top three weren't yet at the franchise. The Buttler-Gill-Sudharsan unit playing tonight has now beaten Rajasthan twice in two attempts. The H2H window the model uses needs shortening — that is one of two adjustments going into the next prediction iteration.
For the model's part, the Black-Scholes volatility input had flagged this match as a high-variance fixture (confidence 74, not 85+). The probability range was wider than for any RR home match this season. The Oracle whispered it might be wrong. The Oracle, this time, was right to whisper.
Player of the match — the data case
The official POTM nod, when our match-history layer ingests it, is almost certainly going to one of three Gujarat batters who put 229 on the board. Without the granular scorecard yet hydrated in the back end, the data points the editorial team is watching:
- The opening stand: Gujarat lost only four wickets across 20 overs at 11.45 per over. That kind of platform is built by a 60+ off the top.
- The middle-over acceleration: scoring rate held above 11 right through overs 7–15. That requires a sustained second- or third-wicket partnership in the 70–100 range.
- Six count: Gujarat's death-overs surge implies a finisher (likely Sudharsan or Glenn Phillips) cleared the ropes four or more times in the last four overs.
Editorial bias, pending official confirmation, is that Buttler walks away with it. Returning to his old home ground, against the franchise that built his T20 brand, in conditions that historically dismissed him cheap, he scored at a rate that broke the chase open. If it isn't Buttler, it's Gill, and the data case is interchangeable. The point, for Oracle's accountability ledger, is that this kind of innings was inside our distribution — we simply didn't push enough probability mass towards it.
What this means for both teams' next fixture
Rajasthan Royals — the playoff math just got brittle
Rajasthan now sit on the cliff edge. The 77-run defeat does not just cost two points; the net run-rate hit is one of the largest swings of their season. With a handful of matches still to play, the Royals need to win the bulk of them and likely engineer a 30+ run / 30+ ball margin in at least one to keep their NRR competitive. The bowling group needs a hard reset. Sandeep Sharma's economy has crept above ten. Archer's wide rate is at a season-high. Without those numbers correcting, finishing inside the top four becomes a stretch rather than an expectation. CricMind's Oracle will publish a dedicated retrospective-adjusted prediction for their next fixture once the playing XI is confirmed.
Gujarat Titans — playoff lock tightens
Gujarat move to a position where two more wins likely seal a top-four berth. The bigger story for Shubman Gill's side: this is back-to-back away wins by a 50+ margin. The Titans' away win-rate has historically lagged their home record by close to 20 percentage points across all IPL seasons. That gap, in 2026, has closed. The model will be re-weighting that going forward. The Buttler-Gill axis, in particular, is now the strongest opening pair in the league by powerplay strike-rate this season. That metric was being treated as a four-match sample three weeks ago. It is no longer a sample — it is a property of the side.
Season accuracy update — Oracle scorecard
After Match 52, the running Oracle scorecard reads as follows:
| Metric | Value |
|---|---|
| Settled matches graded | 51 (excluding 1 no-result) |
| Correct calls | 27 |
| Wrong calls | 24 |
| Season accuracy | 52.9% |
| Matches still pending | 48 |
The model has now missed three of its last five. That is not a season-defining streak yet — variance in T20 cricket is a permanent companion — but the pattern is consistent enough to warrant the two adjustments the post-mortem above flagged: shorten the H2H window, and re-weight EMA when the underlying matches are low-scoring outliers. Both go into the model's next training pass before the upcoming round of fixtures.
Honest framing: 52.9% across 51 graded T20 matches is roughly in line with the closing odds of professional betting markets and modestly ahead of consensus expert picks tracked by mainstream cricket coverage. It is also visibly below where this engine should be performing once the live in-match Meso and Micro layers come online for the playoffs. The accuracy tracker on the homepage updates automatically — and stays public, win or lose. That is the bargain the Oracle makes with the reader.
FAQ
Who won IPL 2026 Match 52 between Rajasthan Royals and Gujarat Titans?
Gujarat Titans won by 77 runs at Sawai Mansingh Stadium on 9 May 2026. Gujarat posted 229/4 in their 20 overs at a run-rate of 11.45 and bowled Rajasthan out for 152 in 16.3 overs. It was one of the most one-sided results of the season.
Who was the player of the match?
Detailed scorecard data is being ingested into the match-history layer; once confirmed, the official POTM will appear on the match page. Editorial expectation, based on the team-level batting numbers, is that the award goes to a Gujarat top-order batter — most likely Jos Buttler or Shubman Gill, with Sai Sudharsan a third candidate.
What did CricMind's Oracle predict before the match?
The Oracle backed Rajasthan Royals at 51% to Gujarat Titans' 49% with a 74-point confidence reading. The top three factors driving that lean were EMA Recent Form (+11.2%), Head-to-Head (+6.0%), and Venue Intelligence (+5.3%) — all of which favoured Rajasthan. All three failed against the actual result, which is why this counts as a clear miss rather than a marginal one.
Why did the model get this match wrong?
Three reasons surfaced in the retrospective. First, EMA recent form was over-weighted because Rajasthan's recent wins came in low-scoring matches that masked a bowling vulnerability on high-scoring surfaces. Second, the head-to-head window was too long — career-spanning data does not reflect the current Buttler-Gill-Sudharsan trio's match-up profile. Third, Sawai Mansingh's recent venue average has crept higher than the rolling figure the model used.
What does this loss mean for Rajasthan Royals' playoff hopes?
With a handful of matches still to play, Rajasthan likely need the majority of their remaining fixtures to go their way and a positive net run-rate swing to keep their playoff math credible. The 77-run defeat dented their NRR significantly. The bowling unit, in particular, needs a hard reset before the back end of the season.
What does this win mean for Gujarat Titans?
Gujarat are now strong favourites for a top-four playoff berth. Two more wins likely seal it. Their away record in 2026 has now closed the historical gap with their home record — a structural shift that will be re-weighted in future Oracle prediction runs.
What is CricMind's Oracle prediction for the next round of matches?
Pre-match Oracle calls for the next round of IPL 2026 fixtures, including Chennai Super Kings vs Lucknow Super Giants and Royal Challengers Bengaluru vs Mumbai Indians, are published on each individual match page. The factor breakdowns are live now, and every probability number will be graded against actual results in the same Oracle Retrospective format you just read.