Lucknow Super Giants Vs Rajasthan Royals Match Scorecard: The Complete IPL 2026 Story

Three ducks in three overs. That’s how Lucknow Super Giants’ innings started in Match 32 against Rajasthan Royals Ayush Badoni run out, Rishabh Pant dismissed, then Aiden Markram gone too.

By the time Rajasthan met Lucknow again in Match 64, the story flipped entirely. This time it was Rajasthan’s top order that collapsed to 32/3, yet they still walked away with the win.

Here’s the real problem most scorecard pages miss: they treat these as two separate, unrelated matches. What most people miss is that both games followed an almost identical script a brutal top-order collapse followed by a partial recovery yet Rajasthan won both times. That pattern matters far more than any single scoreline.

Both Meetings At A Glance

Rajasthan Royals swept both IPL 2026 meetings against Lucknow Super Giants, first by 40 runs at Ekana, then by 7 wickets at Jaipur.

Match	Date	Venue	Result
Match 32	April 22, 2026	BRSABV Ekana Stadium, Lucknow	Rajasthan Royals won by 40 runs
Match 64	May 19, 2026	Sawai Mansingh Stadium, Jaipur	Rajasthan Royals won by 7 wickets

What people think vs reality: fans assume a season sweep means Rajasthan simply outclassed Lucknow both times. Reality both matches featured a Rajasthan top-order collapse before their eventual win, proving this wasn’t one-sided dominance but genuine resilience under pressure.

Match 32: Rajasthan’s Top-Order Collapse, Then Recovery

Rishabh Pant won the toss and invited Rajasthan to bat first at Ekana. It looked like a masterstroke almost immediately.

RR’s Batting Collapse and Rescue

Phase	Score	What Happened
Top-order collapse	32/3	Jaiswal and Jurel dismissed off back-to-back deliveries by Shami, Mohsin Khan added a wicket-maiden
Middle-order rebuild	62/5	Parag and Hetmyer added 30 off 30 balls before both fell in their 20s
Late acceleration	159/6	Jadeja (43* off 29) and Impact Player Shubham Dubey (19 off 11) rebuilt again

Read Also:- Lucknow Super Giants Vs Delhi Capitals Match Scorecard

Mohammed Shami dismissed Yashasvi Jaiswal and Dhruv Jurel off consecutive balls in the third over, after Rajasthan had raced to three boundaries earlier in the same over. This is where things go wrong for most match reports they call this a “collapse” and move to the recovery. What they miss is the sheer speed of the reversal: Rajasthan went from looking like they’d post 200-plus to fighting for a defendable total within four overs.

The Impact Player Decision That Changed Everything

Rajasthan sent in Shubham Dubey as their Impact Player substitution specifically to add lower-order firepower. My bold take: this single tactical call, more than any individual innings, is why Rajasthan reached a defendable 159 instead of collapsing to under 130. Jadeja’s unbeaten 43 off 29 balls anchored the finish, but Dubey’s quick 19 gave him someone to actually farm the strike with.

LSG’s Chase: A Mirror-Image Collapse

Lucknow’s reply started even worse than Rajasthan’s innings had. Ayush Badoni was run out in the very first over, and Rishabh Pant lost his wicket in the second, leaving Lucknow at 10/2. Aiden Markram fell in the third over, meaning three of Lucknow’s top batters registered ducks in a single innings.

Batter	Runs	Balls	Note
Ayush Badoni	0	—	Run out, 1st over
Rishabh Pant	0	—	Dismissed 2nd over
Aiden Markram	0	—	Dismissed 3rd over
Nicholas Pooran	22	25	Tried to rebuild, too slowly
Mitchell Marsh	55	41	Top scorer, dismissed 16th over by Burger

What most people miss: even Marsh’s fighting 55 couldn’t rescue an innings already lost after three ducks inside three overs. Lucknow were skittled for 119 in 18 overs, handing Rajasthan a 40-run win.

A Bold Observation On This Match

There’s a pattern worth naming directly: when three of your top-order batters go for zero in the same innings, no individual fifty from the middle order can realistically save the game. Marsh’s 55 looked good on the scorecard, but it came too slowly against a required rate that had already spiraled out of control by the sixth over.

Match 64: Sooryavanshi’s Blitz Seals The Sweep

By May 19 at Jaipur, Lucknow batted first and posted a much stronger 220/5 in 20 overs. This time, the pressure was on Rajasthan to chase a genuinely competitive total.

The Chase: 225/3 In 19.1 Overs

Rajasthan completed the chase with 225/3 in 19.1 overs, winning by 7 wickets with five balls to spare. Vaibhav Sooryavanshi’s explosive innings was the difference-maker, described by commentators as an “incredible blitz” that carried Rajasthan to victory.

Team	Score	Result
Lucknow Super Giants	220/5 (20 overs)	Set a strong target
Rajasthan Royals	225/3 (19.1 overs)	Won by 7 wickets

What people think vs reality: fans assume chasing 220-plus and winning by 7 wickets with an over to spare means a comfortable night. Reality Lucknow’s total of 220 was genuinely stiff for this ground, and Rajasthan needed a near-perfect middle-overs partnership to get there without late-innings panic.

Why Sooryavanshi’s Innings Mattered So Much

This is where things go wrong for most highlight reels they show the six-hitting and move on without explaining the context. Sooryavanshi’s innings came in a chase where losing early wickets against a 220-run target would have put Rajasthan under serious pressure. Instead, his acceleration meant Rajasthan never had to play catch-up cricket in the back half of the chase.

A Second Bold Take

My honest read: Rajasthan’s think tank deserves genuine credit for building a batting unit that can absorb an early top-order failure (as seen in Match 32) and still find a way to either defend a modest total or chase a big one comfortably (as seen in Match 64). That’s not luck repeating twice that’s actual squad depth doing its job.

The Bigger Pattern Across Both Matches

Looking at both scorecards together reveals something neither match shows in isolation. Rajasthan’s top order failed in Match 32 (32/3), yet they still won. Lucknow’s top order failed in the same match (10/2 with three ducks), and they lost badly. In Match 64, Rajasthan chased successfully without needing a similar rescue act.

Factor	Match 32	Match 64
Winning team’s top-order start	Rajasthan struggled (32/3)	Rajasthan chased cleanly
Losing team’s top-order start	Lucknow collapsed (10/2, 3 ducks)	Lucknow posted 220/5
Impact Player influence	Shubham Dubey’s 19 off 11 was crucial	Less pivotal, chase relied on top-order form
Result margin	40 runs	7 wickets

Read Also:- South Africa National Cricket Team Vs India National Cricket Team Matches

What most people miss: Lucknow actually batted far better in Match 64 (220/5) than in Match 32 (119 all out), yet still lost both games. That tells you Rajasthan’s bowling and chasing composure, not just Lucknow’s batting failures, decided both results.

What Both Franchises Should Actually Do Next

These two matches expose clear, fixable patterns for both teams heading into the rest of the season. What should analysts and fans actually track going forward?

• Watch Lucknow’s top three closely in upcoming matches, since three ducks in three overs during Match 32 points to a genuine technical vulnerability against quality new-ball bowling
• Track Rajasthan’s Impact Player usage pattern, since sending in Shubham Dubey specifically for lower-order firepower in Match 32 is a repeatable tactical template worth watching again
• Follow Vaibhav Sooryavanshi’s form in the coming weeks, since his Match 64 blitz suggests he’s becoming Rajasthan’s genuine middle-overs matchwinner
• Compare Mitchell Marsh’s strike rate across both matches, since his 55 in Match 32 came too slowly to matter, and Lucknow needs him accelerating earlier in future chases

For Lucknow Super Giants specifically, the practical decision is clear: address the top-order fragility before facing Rajasthan or any other strong new-ball attack again, since this exact weakness cost them Match 32 outright and nearly did the same in Match 64.

Frequently Asked Questions