Gill's 84, Sudharsan's 55, and a Rashid Khan Spell So Complete the Sawai Mansingh Crowd Watched Their Team Disintegrate by 77 Runs as Gujarat Titans Climbed to Second on the Table With a Fourth Consecutive Win
Gujarat Titans — playing the most assured cricket of their season — posted 229 for 4 at Sawai Mansingh Stadium on the back of a Shubman Gill–Sai Sudharsan opening stand of 118, then watched Rashid Khan dismantle Rajasthan Royals' chase with figures of 4 for 36 and Jason Holder strangle the lower order with 3 for 12, sealing a 77-run victory that became GT's largest in IPL history by margin of runs and announced, with the kind of clarity that the points table demands at this stage of the season, that the franchise that sat sixth a fortnight ago is now the team most other contenders would prefer not to draw in the playoffs.
Sawai Mansingh on a Hot Jaipur Night — Where Rajasthan's Fortress Was Stormed by a Team That Has Suddenly Remembered How Good It Is
The Sawai Mansingh Stadium on a May evening is one of Indian cricket's more atmospheric venues — the dry desert air that still carries the warmth of the afternoon, the pink-stoned outline of the city visible from the upper tiers, and a crowd that has watched Sanju Samson's Royals turn this ground into a fortress over the past three seasons. 182 is the average first-innings score here in IPL 2026, a number that tells you the surface is good for batting but not impossible to defend, and the team that wins the toss usually elects to field knowing that the dew, when it arrives around the eighth over of the second innings, transforms the bowling conditions in ways that make chasing a more comfortable proposition than defending.
What happened on Saturday evening was therefore not what the script suggested. Rajasthan won the toss, opted to bowl, and walked off the field at the innings break staring at a scoreboard that read 229 for 4 — Gujarat Titans' biggest IPL total away from Ahmedabad, and a number that immediately reframed the contest as a question of damage control rather than victory. The dew arrived. It mattered for about four overs. And then Rashid Khan arrived, the surface began to grip in ways that only the sharpest leg-spinner in the format can exploit, and the Royals — who had been 86 for 3 after seven overs and still in some kind of contest — collapsed for 152 in 16.3 overs, the fourth-largest defeat by margin of runs that this Royals franchise has suffered in front of its home crowd.
The Sawai Mansingh wicket, which had behaved like a typical Jaipur belter through the first innings, became something different the moment GT's spinners took the ball. The ball that had skidded on for Gill and Sudharsan now gripped and held. The boundaries that had been cleared with the kind of timing that makes the work of fast bowlers thankless became unreachable as Rashid pitched into the rough that the seamers had created. And the home crowd — which had begun the night with the optimism that 230 was chaseable on a true surface and ended it with the sober realisation that their team had been comprehensively outplayed — watched their playoff hopes thin to the kind of mathematical possibility that requires net-run-rate calculations and other-team scoreboards to remain alive.
There are bowlers who win matches with new-ball wickets. There are bowlers who win matches with death-overs yorkers. And then there is Rashid Khan, who wins matches in the middle overs of an innings that has not yet decided whether it wants to be a chase or a collapse — and who, on Saturday evening at Sawai Mansingh, produced the kind of spell that reminded everyone watching why the Afghan leg-spinner has been the most consistent T20 bowler in world cricket for the better part of a decade.
Rajasthan were 86 for 3 in the seventh over when Rashid was thrown the ball. The required rate was climbing past 12 an over, but with Riyan Parag, Dhruv Jurel, and Shimron Hetmyer all in the dressing room — even if not all at the crease — the chase was still in territory that an in-form Rajasthan side had successfully navigated in previous seasons. Rashid's first over conceded six runs and produced no wickets. His second over conceded eight. And then, in his third, the leg-break that Jurel attempted to slog through midwicket spun past the bat with the inevitability of a delivery that had been planned three balls in advance, the ball clipping the off stump with a sound so quiet it seemed almost apologetic for what it had just done to a contest that, until that moment, had still been a contest.
The wickets that followed were not surprises. They were the natural consequences of a bowler operating at the height of his powers on a surface that had begun to grip and a chase that had begun to panic. 4 for 36 in 4 overs — Player of the Match by the kind of margin that statisticians prefer not to bother quantifying — and a spell that, more than any other passage of play, will be remembered as the moment when GT's late-season surge stopped being a question and started being an answer. At 325 career IPL wickets and counting, Rashid Khan in May, on a gripping surface, against a batting order that does not have a designated leg-spin specialist, is the closest thing this format has to a controlled experiment in match outcomes.
For three weeks of IPL 2026, Shubman Gill's captaincy had been quietly impressive while his batting had been quietly disappointing. 32 off 24 at the Chinnaswamy. 33 off 33 at Chepauk. The kind of starts that promise hundreds and produce middling thirties — innings that demonstrated his class without ever quite weaponising it. On Saturday evening at Sawai Mansingh, Gill stopped promising and started delivering, and the 84 off 44 that anchored GT's innings was the captain's knock that this season had been waiting for him to play.
The cover drive off Trent Boult in the second over — played with a stillness of head that the coaching manuals dream about, the bat coming down in a vertical line that bisected mid-off and cover with a precision that made the boundary look inevitable — was the early signal that Gill had decided to translate technique into intent. The ramp shot over short third in the powerplay against Avesh Khan's cross-seam delivery was the moment when the technical batter revealed the modern stroke-maker beneath. And the slog-sweep over deep midwicket against Yuzvendra Chahal's flighted leg-break — a shot that Gill plays only when he is in the kind of form where the pre-meditated risk feels mathematically safe — was the innings' confirmation that the captain was operating on a different plane to everyone else on the field.
The dismissal — caught at long-on attempting one big shot too many off Sandeep Sharma's cutter in the seventeenth over — was the only moment in the innings where Gill betrayed the slightest discomfort, and even that was the discomfort of a batter trying to convert a half-century into a hundred rather than the discomfort of a batter trying to survive. 9 fours, 4 sixes, a strike rate just under 191, and a 118-run opening partnership with Sai Sudharsan that ended only because Gill chose to risk dismissal in pursuit of acceleration. For the captain whose form has been the one sustained question mark over GT's resurgence, Saturday's innings was the answer that erases the question.
The records that Sai Sudharsan has accumulated this IPL season have begun to assume the inevitability of weather forecasts — you know the rain is coming, you just don't know exactly which evening. 55 off 36 at Sawai Mansingh added another fifty to a season that has produced match-winning contributions with the kind of regularity that selection committees notice and broadcasters celebrate. The 118-run opening stand with Gill set the platform from which everything else followed, and Sudharsan's role in that partnership — playing the foil to Gill's aggression for the first ten overs before accelerating in his own measured way through the middle — was the kind of contribution that does not always make highlight reels but that absolutely makes match results.
What distinguishes Sudharsan from the merely stylish is the patience that sits beneath the technique. The drive that does not chase the ball wide of off stump but waits for it to come into the slot. The pull shot that does not try to clear the rope but settles for the placed boundary in front of square. And the running between the wickets — the singles taken to deep cover, the converted twos that other batters would treat as routine ones, and the calling that suggests a batter operating with the kind of awareness that turns 60-ball innings into 70-ball innings without anyone quite noticing the gear change. The dismissal — caught at deep midwicket attempting a hook off Maheesh Theekshana's slower ball — came at the moment when the platform he had built with Gill was being handed to Jos Buttler and Washington Sundar for the acceleration phase. That phase produced Washington's unbeaten 37 off 18, Tewatia's late cameo, and the kind of 18-run final over that converts 211 into 229 — the difference between a competitive total and a match-winning one.
The wickets in the scorecard read Rashid Khan as the Player of the Match, but the bowler who finished the contest was Jason Holder, whose 3 for 12 in 3.3 overs dismantled the Rajasthan tail with the methodical ruthlessness of a man who has bowled enough death overs in international cricket to know exactly how to convert a collapsing innings into an inevitable defeat. The West Indian's tall release point — that high arm that allows the ball to come down at the batter from an angle that makes the bouncer feel taller and the yorker feel fuller — has been GT's most underrated weapon this season, and on Saturday evening, Holder was the bowler who turned a hopeful collapse into a final scoreline that read 152 all out.
The dismissal of Hetmyer, caught at long-off attempting to clear the rope when the asking rate had moved into territory that demanded boundaries from every ball, was the moment when the Royals' last realistic hope evaporated. The yorker that pegged back Sandeep Sharma's middle stump — bowled at 141 kph with a precision that Holder, at 6'7", makes look like the natural extension of his frame — was the delivery that completed Rashid's work and left only Brijesh Sharma's defiant 1 not out standing between the Royals and the worst defeat of their season. Three wickets for twelve runs in three and a half overs is the kind of analysis that wins the Player of the Match award in seven matches out of ten. On Saturday evening, with Rashid Khan in the same dressing room operating at the height of his powers, Holder's contribution was the supporting performance that the leg-spinner's masterpiece could not have happened without.
The Numbers That Tell the Story of a 77-Run Demolition
| Final Result | GT 229/4 (20) beat RR 152 all out (16.3) by 77 runs — GT's largest victory in IPL history by margin of runs (previous best: 62-run win vs LSG) |
| GT's Top Order | Gill 84(44) — 9 fours, 4 sixes, SR 190.9; Sudharsan 55(36) — SR 152.7; opening stand 118 in 12.2 overs — the foundation on which the total was built |
| GT's Death-Overs Surge | Washington Sundar 37* off 18 (3 fours, 2 sixes); Tewatia's late cameo; final-over 18 runs converted a competitive 211 into a match-winning 229 |
| Rashid Khan — Player of the Match | 4 for 36 in 4 overs — wickets of Jurel, Parag, Hetmyer's set-up, plus Theekshana; the spell that broke the chase between overs 8 and 14 |
| Jason Holder's Finish | 3 for 12 in 3.3 overs — economy 3.43, the second-most damaging spell of the night; closed out the Royals tail with full deliveries that the surface could not absorb |
| RR's Collapse Pattern | 86/3 after 7 overs (in the contest) → 152 all out in 16.3 (out of it); 7 wickets lost for 66 runs in 9.3 overs once Rashid took the ball |
| Points Table Impact | GT to 2nd with 14 points — fourth consecutive win, NRR boosted past +0.6; RR fall to fifth, playoff path now requires both wins and external help |
| GT's Resurrection Arc | From 6th place a fortnight ago → four straight wins (RCB at Chinnaswamy, CSK at Chepauk, MI at Wankhede, RR at Sawai Mansingh) → second on the table heading into the final week |
The numbers describe a match that was decided not by a single passage of play but by the cumulative weight of a team operating at the peak of its powers against a team whose form had begun to fray at exactly the wrong moment. GT scored at 11.45 runs per over with the bat. They conceded at 9.21 runs per over with the ball — but more importantly, they took wickets at a rate of one every 9.9 deliveries once Rashid was introduced, the kind of strike rate that does not allow a chasing team to build the partnerships that big chases require. The 77-run margin is the headline. The collapse pattern — seven wickets for sixty-six runs in just over nine overs — is the story.
To understand what Saturday evening at Sawai Mansingh meant for Gujarat Titans, you have to go back to May 29, 2022, when a franchise that had not existed eight months earlier lifted the IPL trophy at the Narendra Modi Stadium in front of a hundred thousand fans who had adopted this team with the urgency of a city that had waited decades for its own identity in the world's biggest cricket league. Hardik Pandya captained that side. Rashid Khan — released by SRH and considered, by some, to be on the wrong side of his peak — was the bowling fulcrum. And a young opener named Sai Sudharsan, who most casual fans had not yet heard of, scored a half-century in the final and announced himself to the cricket world as the next great thing.
That 2022 title was won on the back of a culture that GT have spent four seasons trying to preserve and occasionally trying to recover. The team that began this IPL with a 99-run home defeat to Mumbai Indians had drifted from that culture. The team that demolished Rajasthan by 77 runs on Saturday evening was the team that had remembered it. Rashid Khan taking four wickets in a chase. Sai Sudharsan anchoring an opening stand of 118. The captain — Pandya in 2022, Gill in 2026 — leading from the front with a knock that turned promise into proof. The Titans, when they are at their best, win matches in a particular way: through batting depth that compensates for top-order failures, through a leg-spin masterclass in the middle overs, and through an all-round attack that includes someone who can finish an innings with the new ball or the old.
The four-season journey from Pandya's debut-season triumph to Gill's late-season surge in 2026 has not been linear. There have been seasons of mid-table mediocrity, of injury crises, of selection debates that questioned whether the franchise's identity was a one-off or a sustainable model. Saturday evening at Sawai Mansingh was the latest evidence that the model is sustainable — and that when GT's batting top order, leg-spin attack, and all-round depth align, this is the side that no other team in IPL 2026 wants to draw at this stage of the tournament. Rajasthan Royals, who have built their own identity on the foundations laid by Shane Warne in 2008 and refined by Sanju Samson's leadership across the past three seasons, found out on Saturday what the rest of the league has begun to suspect: GT in form is the franchise whose history rhymes most often with the kind of ending that ends in a trophy.
How the Match Was Won — And What This Result Means for Both Teams in the Final Week of the League Stage
The 77-run margin obscures how close this match was for the first thirty-eight overs of cricket and how decisively it was settled in the seven overs that followed. Rajasthan won the toss, made the right decision to bowl, and bowled with discipline through the powerplay — 52 for 0 at the end of the first six overs is competitive containment by any T20 standard, and on a different evening, against a different opening pair, that opening burst would have been the platform from which the chase was eventually won. But the GT openers absorbed the powerplay's pressure, accelerated through the middle overs with the patience of a partnership that understood the value of wickets in hand, and handed over the innings to Buttler and Washington Sundar at 155 for 1 in the fourteenth — a position from which 220-plus was not just possible but probable.
The Royals' chase began with the right intent. Yashasvi Jaiswal and Jos Buttler — wait, Buttler plays for GT now, an irony that was not lost on the commentators when the cameras kept finding him in the GT dugout watching Sanju Samson open with Yashasvi Jaiswal — combined for a powerplay partnership that put RR at 62 for 1 after six overs, the kind of start that implied the chase was on. And it was on, until Rashid Khan began his spell. The leg-break that bowled Jurel. The googly that trapped Parag in front. The wicket-to-wicket consistency that gave the home batters no width to free their arms and no length to step into. Once Rashid had the surface gripping, the rest of the chase was an exercise in delaying the inevitable rather than reversing it.
Holder's death-overs work closed the contest with the kind of efficiency that the scorecard reflects but the highlights packages tend to under-celebrate. Brijesh Sharma's unbeaten 1 at the end of the innings — a number that captures the totality of the collapse better than any other single statistic — left the Royals all out for 152 in 16.3 overs, with overs to spare and damage to the net run rate that may matter when the playoff race comes down to fractions in the final week.
For Gujarat Titans, this is the win that confirms the resurrection. Four matches ago, they were sixth on the table and considering whether playoff qualification was realistic. They are now second, with 14 points, an upward NRR trajectory, and a fixture list that includes winnable matches against teams whose form has begun to plateau. Sudharsan's consistency, Gill's return to form, Rashid's peak, Holder's under-celebrated all-round contributions, and the depth that turns 211-or-bust scoreboards into 229s — these are the components of a side that is not merely making up the playoff numbers but is genuinely capable of winning the title from second on the table.
For Rajasthan Royals, the path forward is harder. Fifth on the table, with a damaged net run rate, with a home defeat that has shaken the certainty their Sawai Mansingh fortress was supposed to provide, and with two matches remaining against opponents who are themselves in the playoff race, the Royals must now win both and rely on results elsewhere. Sanju Samson's leadership — which has been the franchise's defining quality across three seasons — faces its sternest test of the year. The squad has the talent. The form, after Saturday evening, requires the kind of recovery that only good teams produce when the stakes are at their highest.
One match. Two trajectories. A points table that has just rearranged itself in ways that will shape the final week of the IPL 2026 league stage. Saturday evening at Sawai Mansingh was the kind of result that, in May, tells you which teams are peaking and which are fading — and the Titans, in case anyone was still in doubt, are peaking at exactly the moment of the season when peaking matters most.
What does GT's late-season surge mean for the playoff bracket? Does Rajasthan have a realistic path to qualification, and if so, what combination of results would they need? How does Rashid Khan's form compare to his Player of the Tournament 2022 peak, and what does the data say about his match-winning probability on the surfaces GT will encounter next?
Our Match Analyzer has the full post-match breakdown for RR vs GT — wagon wheels, partnership impact charts, win-probability curves at each over, and the playoff-permutation model that updates after every match. Unlock CricIntel Pro for AI-powered match predictions that go deeper than any review can.
Predicted Playing XI for Both Teams
Our AI predicts the most likely starting 11 for each team based on current Orange/Purple Cap form, recent starter patterns, and role fit. Constraints applied: 1 keeper, 4-5 batters, 2-3 all-rounders, 3-4 bowlers, max 4 overseas. Updates daily at 3 AM IST.
- 1Dhruv JurelWicket-KeeperStarted 2 of last 3 · Automatic XI pickScore32
- 2Yashasvi JaiswalBatterStarted 2 of last 3 · Automatic XI pickScore32
- 3Shimron HetmyerOverseasBatterStarted 2 of last 3 · Automatic XI pickScore32
- 4Vaibhav SuryavanshiBatterStarted last matchScore18
- 5Riyan ParagAll-RounderStarted 2 of last 3 · Automatic XI pickScore32
- 6Ravindra JadejaAll-RounderStarted 2 of last 3 · Automatic XI pickScore32
- 7Donovan FerreiraOverseasAll-RounderStarted 2 of last 3 · Automatic XI pickScore32
- 8Jofra ArcherOverseasBowlerStarted 2 of last 3 · Top-15 bowler · Automatic XI pickScore49
- 9Ravi BishnoiBowlerStarted 2 of last 3 · Top-15 bowler · Automatic XI pickScore41
- 10Nandre BurgerOverseasBowlerStarted 2 of last 3 · Automatic XI pickScore32
- 11Sandeep SharmaBowlerStarted 2 of last 3 · Automatic XI pickScore32
- 1Jos ButtlerOverseasWicket-KeeperStarted last match · Top-15 batter · Automatic XI pickScore27
- 2Shubman GillBatterStarted last match · Top-5 batter (#4) · Automatic XI pickScore40
- 3B. Sai SudharsanBatterStarted last match · Automatic XI pickScore18
- 4M. Shahrukh KhanBatterSquad regularScore5
- 5Rashid KhanOverseasAll-RounderStarted last match · Top-15 bowler · Automatic XI pickScore37
- 6Rahul TewatiaAll-RounderStarted last match · Automatic XI pickScore18
- 7Washington SundarAll-RounderStarted last match · Automatic XI pickScore18
- 8Kagiso RabadaOverseasBowlerStarted last match · Top-5 bowler (#1) · Automatic XI pickScore43
- 9Mohammed SirajBowlerStarted last match · Top-15 bowler · Automatic XI pickScore34
- 10Prasidh KrishnaBowlerStarted last match · Top-15 bowler · Automatic XI pickScore31
- 11Ishant SharmaBowlerStarted last match · Automatic XI pickScore18
How is this calculated?
Composite Score (0-100) blends four signals per player:
- Current-season form (35%) — Position in Orange Cap (top batters) or Purple Cap (top bowlers). #1 worth more than #15.
- Regular-starter rate (25%) — How often they've been in the confirmed XI across past matches.
- Role fit + base form (20%) — Squad-level form rating and role suitability.
- Match availability (filter) — Injured / ruled-out players excluded.
Final XI is constrained: max 4 overseas, exactly 1 keeper, role-balanced. Confirmed XIs (after toss) override predictions automatically when available.