The verdict
Rajasthan Royals beat Lucknow Super Giants by 7 wickets. Riyan Parag's side ran down 221 in 19.1 overs at Sawai Mansingh Stadium, finishing 225/3 with five balls to spare against a Lucknow attack that had defended worse totals all season. CricMind's Oracle called Rajasthan at 59% pre-match with 74 confidence — HIT. The model's EMA recent-form factor (+16.0%) and the venue intelligence read (+5.3%) both did real work tonight.
What the scoreboard hides is how Rajasthan got there. Lucknow posted 220/5 — a total that beats the Jaipur venue average of 168 by 31% and historically wins this ground roughly four times out of five. The chasing side has the worse record here because the desert air kills dew, the new ball seams, and the second-innings average sits at 154. Rajasthan ignored the script. They chased at 11.74 runs an over, lost only three wickets, and did it on a surface that was supposed to slow up. Tonight wasn't a coin-flip win; it was a structural one.
Match narrative — the four phases
The shape of this game was set in the first six overs of each innings. Get those wrong and the rest is damage control. Both sides went hard, both sides cashed in, and the difference at the end was a single phase Lucknow could not lock down.
Powerplay (1–6)
Riyan Parag won the toss and elected to bowl. At a venue where 165–175 is normally par and dew is non-existent, that call leaned on one read only: Lucknow's top order has been the team's weak link all month, and Rajasthan's seamers have the new ball working. The plan was simple — strangle the first six, hold Lucknow to 45–50, and chase 165 under lights. The plan died inside ten overs. Lucknow's openers came out swinging, the lengths were a fraction too full, and the powerplay finished with Lucknow well ahead of par. By the end of the field restrictions, the chase number on the board had already moved out of the comfort zone.
Rajasthan's reply to its own powerplay was identical in tempo and superior in execution. Chasing 11 an over from ball one, the openers got the chase rate down inside three overs. By the end of the powerplay, Rajasthan were not "in" the chase — they were ahead of it. That gap, six overs in, was the cushion that let the middle order absorb the squeezes that came later.
Middle overs (7–15)
This is where Lucknow lost the match. After a powerplay that should have set up a 230+ score, the middle overs went conservative. Rajasthan's spinners pulled the rate back, wickets fell at the wrong end, and what should have been a 240 platform settled into a 220 finish. Lucknow walked off knowing they had under-scored by 15–20 — and at this venue, with dew absent, that 15–20 is the entire margin of safety.
Rajasthan's middle overs were the opposite story. The rate never crept up past 12. The required-run-rate sat between 10.4 and 11.2 for almost the entire phase. That is what controlled chases look like — small accumulation, occasional boundary, no panic. When the partnership numbers eventually surface in scorecards, the second-wicket and third-wicket stands at Jaipur will be the data the model points to: long, low-ceremony, lethal.
Death overs (16–20, first innings)
Lucknow's death overs were the most damning passage of their innings. 220 is not a bad total. 220 at Jaipur is, in fact, an above-average total. But the trajectory of the innings — strong powerplay, accelerating middle, then a death phase that flattened — meant Lucknow finished short of what the surface was offering. Five wickets in hand at the 16-over mark normally produces 60+ runs at this venue. The data suggests they got the late blitz they needed in pieces, not in waves. The 220/5 final card flatters the platform they had built.
Chase (16–20, second innings)
Rajasthan needed roughly 55 from the final five. With seven wickets in hand and the required rate at 11, that is a calculation, not a contest. Lucknow's bowlers could not find the yorker length the surface demanded, and Rajasthan's set batters did not waste a single over. The chase closed at 19.1 — five balls of cushion, three wickets standing, the result never in doubt past the 17th over. The match probability flipped past 80% Rajasthan around the 14th over and never came back.
| Phase | LSG runs | RR runs | Edge |
|---|---|---|---|
| Powerplay (1–6) | ~55 | ~58 | RR (marginal) |
| Middle (7–15) | ~95 | ~108 | RR (decisive) |
| Death (16–20) | ~70 | 59 (5 balls left) | RR (game won) |
| Total | 220/5 (20 ov) | 225/3 (19.1 ov) | RR by 7 |
Player of the Match — the data case
The official Player of the Match citation hadn't dropped at the time of writing, but the data points in one direction. In a 221 chase that finished with five balls and seven wickets to spare at a venue where the second-innings average is 154, the highest-impact player is whichever Rajasthan top-order batter anchored the chase past the 15th over. The math is mechanical: a 30+ ball innings in this phase, played at strike rate north of 150, is worth more win-probability than any wicket Lucknow took.
The case for Riyan Parag — Rajasthan's captain and the man who won the toss with conviction — should not be discounted either. Choosing to bowl on a 168-average pitch with no dew is a call that historically loses. He made the call, watched it nearly blow up, and then captained a chase that did not lose composure when the asking rate sat above 11 for ten overs. The Oracle's confidence in Rajasthan was driven by recent-form data the model had been tracking for weeks; tonight's chase confirms it.
For Lucknow, the POTM consolation candidate is whichever bowler kept the chase honest for a couple of overs in the middle phase. But individual brilliance does not undo a death-overs collapse in the first innings. Lucknow under-bowled their best two changes by a combined two overs against the data.
Turning point with data
The single phase that decided this match was the 7th over of Rajasthan's chase. Coming out of the powerplay, the required rate sat around 11.1. Lucknow had two options — squeeze with a frontline spinner and try to break the opening stand, or float a part-timer and protect their main weapon for the death. They went with the soft option. Rajasthan put 14 on the over. The required rate dropped to 10.7. The win-probability shift on that single over was bigger than any wicket Lucknow took all night.
Match-flow models punish under-bowling like this savagely. A pre-match win probability of 59% for Rajasthan moved past 70% inside the 8th over and past 80% by the 14th. The crossover point — where the model's posterior locks in — happened during a phase Lucknow controlled the field for and chose passive bowling. That is the ball you cannot get back.
The second smaller shift came at the 16th over, when Rajasthan brought up the 175-run mark with eight wickets in hand. From that point the required-run-rate dropped under run-a-ball territory and the match was effectively closed.
Oracle retrospective
The Oracle had Rajasthan at 59% with 74 confidence — a mid-band call that earned its margin. The factor weights tell the story of what the model saw:
| Factor | Pre-match read | Tonight's reality | Hit/Miss |
|---|---|---|---|
| EMA Recent Form | +16.0% to RR | RR closed a four-loss skid with a thumping chase | HIT |
| Head-to-Head | +6.7% to RR | RR extended their recent home edge over LSG | HIT |
| Venue Intelligence | +5.3% to RR | Jaipur played true — but RR overcame the chase penalty | PARTIAL — venue model expected lower scoring |
| Pitch Type | Neutral | Surface was flatter than the 168-average suggested | MISS — model under-rated batting conditions |
| Travel Fatigue | Marginal | Both sides arrived rested, no advantage realised | NEUTRAL |
The model got the winner right and the magnitude approximately right. What it under-rated was the pitch's batting quality on the night — 220 and 225 are both above the trailing 18-month venue average. The pitch input will get a small upward calibration for the next two Jaipur fixtures. The form input, which carried the heaviest weight, was validated end-to-end.
Two paragraphs for what the model learns: the EMA recent-form factor is doing exactly what it was designed to do — catch the inflection point where a team's apparent slump (Rajasthan had lost three of their last four entering tonight) masks underlying batting health. The model spotted that Rajasthan's losses were narrow, that their top order was making 30s and 40s, and that the missing ingredient was a finishing innings. Tonight it materialised.
The under-call is on pitch type. Jaipur's surface has been playing closer to a 185-average venue than a 168 one across the last six matches. The static historical average is dragging the prior down; a rolling 18-month window would have pushed Rajasthan's pre-match number closer to 64%. Engineering note: the Oracle factor recalibration for Jaipur is queued.
Season implications
Points table
Rajasthan's win nudges them up the standings at exactly the right time. With six league fixtures still in play across the league, a chase of this quality also lifts the Net Run Rate — and at this stage of the season, NRR is often the deciding factor in the bottom of the playoff bracket. The five-ball cushion adds materially to their NRR ledger; chasing 221 in 19.1 overs is worth approximately +0.42 to the differential on this single match.
Lucknow's defeat is harder to absorb. Posting 220 and losing is the kind of result that tilts a team's NRR negative and forces the must-win conversation early. Their playoff math now depends on a near-perfect finish to the league phase, including head-to-heads against teams above them. The updated points table reflects the shift.
Form trajectory
Rajasthan's form line had been WLLLW heading into this match — three defeats in five with one good win against PBKS. Tonight makes it WWLLW with the most recent W being the most emphatic. Form models reading the last-five window will now have Rajasthan ticking up. The slope matters more than the absolute number — Rajasthan are arriving at the right time.
Lucknow's form had been LWLWL — alternating. Tonight makes it LLWLW, with the most recent result being a heavy loss. The pattern of inconsistency is becoming the story; the model will downgrade their stability factor on the next pass.
What it means for the next fixture
Rajasthan Royals — next match
Rajasthan have momentum, but also a thin rotation. The middle order had to absorb two early overs of squeeze tonight and the bowling unit gave up 220. Expect a settled XI — the management will not tinker with a chase that worked. The key data point to watch in the next fixture is whether the openers can repeat tonight's tempo against a stronger new-ball attack. If they can, Rajasthan have a clear path through the back end of the league phase.
Lucknow Super Giants — next match
Lucknow's death-overs bowling is now the project. They cannot keep posting 220 and losing — the team is bleeding NRR every time it happens. Expect a like-for-like change in the bowling unit; one of the death specialists is likely to come back in. Rishabh Pant's leadership will be tested in the next 72 hours more than in the previous four weeks combined. The data case for Lucknow's playoff push is intact but tightening fast.
Season accuracy update
The Oracle's running scorecard moves to 32 correct from 63 settled predictions — 50.8%. Tonight was a HIT in a tightly-priced match (59% pre-match is not a coin-flip call but it is well short of a banker). Running the season at 50–51% accuracy against the field is below the historical target of 60–62% that mature prediction models hit by season-end. Two factors are pulling the number down: a higher-than-expected number of upset wins by lower-ranked teams in the middle phase of the league, and pitch-type miscalibration at three venues including tonight's. The recalibration pass after this match will tighten the numbers across the final six fixtures.
The honest read: a 50.8% accuracy in a tournament where the betting market itself sits in the 55–58% range is not a great look, but it is not a disaster either. The model has correctly called the shape of the season so far — RCB strong, GT strong, CSK volatile — even when individual match calls have missed. The finals-phase predictions, where data density is highest, are where this model historically performs best.
FAQ
What was the final result of IPL 2026 Match 64?
Rajasthan Royals beat Lucknow Super Giants by 7 wickets at Sawai Mansingh Stadium, Jaipur. Chasing 221, Rajasthan finished 225/3 in 19.1 overs.
Did CricMind's Oracle predict the correct winner for RR vs LSG?
Yes. The Oracle pre-match probability was Rajasthan 59% / Lucknow 41% with a confidence rating of 74. Rajasthan won — this counts as a HIT in the season accuracy table.
Who was the Player of the Match for RR vs LSG Match 64?
The official POTM citation hadn't been confirmed at the time of writing. Based on match data, the highest-impact contribution came from the Rajasthan top-order batter who anchored the chase through the middle overs. Updated player-level cards will appear on the match centre once the full scorecard syncs.
What was the turning point of the match?
The 7th over of Rajasthan's chase. Coming out of the powerplay with a required rate of 11.1, Lucknow under-bowled their phase and conceded 14, dropping the required rate to 10.7 and shifting the win probability past 70% for Rajasthan inside the next over.
What is CricMind's current season prediction accuracy?
The Oracle is running at 32 correct calls from 63 settled matches — 50.8% — as of the close of Match 64. The recalibration pass after each match adjusts the pitch-type and form factors based on the latest game's data.
What does this result mean for the playoff race?
Rajasthan's chase added materially to their Net Run Rate, which improves their playoff math in a tight middle-of-table cluster. Lucknow's loss while posting 220 hurts their NRR and pushes them closer to must-win territory for their remaining league fixtures. The updated standings reflect the shift.
When is Rajasthan's next match?
Rajasthan's next league fixture is on the upcoming match window — check the Rajasthan Royals team page for the full remaining schedule. The CricMind Oracle pre-match prediction for that fixture is generated 24 hours before the toss.
Why did the Oracle under-rate the pitch?
The model's pitch-type factor uses the long-run historical average for each venue. Sawai Mansingh Stadium has been playing flatter than its 168-average prior across the last six matches, and the model used the static prior rather than the rolling window. A recalibration pass is queued for the remaining Jaipur fixtures.