The Eliminator — Where Form Meets Fear: Sunrisers Hyderabad and Rajasthan Royals, 18 Points Against 16, and Only One Survives the Evening at Mullanpur
Sunrisers Hyderabad — third on the table with 18 points, a 2-0 season record against the opposition, and a batting unit that scored 255 in their final league match — face a Rajasthan Royals side that scraped into the playoffs with a do-or-die win over Mumbai Indians, and on a Mullanpur evening where the dew will settle and the careers of half a dozen players could pivot on a single innings, the IPL's most ruthless fixture format asks its oldest question: who wants it more?
The Eliminator — Cricket's Most Unforgiving Format
There is no second chance in an Eliminator. No net run rate to argue over, no favourable schedule to lean on, no mathematical possibility to cling to in the quiet of the team hotel at midnight. You win, you advance. You lose, you go home. And in a tournament that has stretched across sixty days, across seventy league matches, across hundreds of individual performances that have been debated, celebrated, and dissected — it comes down to a single evening in Mullanpur, a single match between two sides whose seasons will be defined by what happens in these forty overs.
Sunrisers Hyderabad arrive at the Eliminator as the side with the superior league record against this opponent — 2-0 in the season, including a remarkable chase of 229 at Jaipur in late April. They finished the league phase with 18 points from 14 matches, level with table-toppers RCB and second-placed Gujarat Titans, separated only by net run rate. Their final league outing — a 55-run demolition of RCB where Abhishek Sharma struck at 254 and Ishan Kishan scored 79 off 46 — was the performance of a side firing on every cylinder. Pat Cummins' return from his lumbar stress injury has restored not just a fast bowler but a captain whose calmness under pressure is worth runs in itself.
Rajasthan Royals, by contrast, squeezed through the door that was closing on them. Their 30-run victory over Mumbai Indians on May 24 — powered by Dhruv Jurel's middle-order composure and Jofra Archer's searing new-ball spell that reduced MI to 24/3 — confirmed the final playoff spot with 16 points. But the Royals arrive with questions that their league-stage performances have not entirely answered. Captain Riyan Parag is carrying a hamstring injury and has admitted he is not fully fit. Ravindra Jadeja is nursing knee and elbow complaints. The aura of invincibility that surrounded this side in March, when they won their first four matches without breaking a sweat, has faded into the memory of a squad that lost its way in the middle passage before finding enough composure to finish inside the top four.
Mullanpur — Neutral Ground, But Not a Neutral Surface
Neither side calls Mullanpur home, and that neutrality is itself a factor. The Maharaja Yadavindra Singh International Cricket Stadium — Punjab Kings' adopted fortress — has been one of the most entertaining venues of IPL 2026. The pitch is a batting surface of the first order: a mix of black and red soil that produces consistent, true bounce, rewards batters who hit through the line, and has turned first-innings totals of 170-180 into the average rather than the aspiration. The highest team score here this season — 254/7 by Punjab Kings against LSG — tells you everything about what this surface is capable of offering to batting lineups willing to be aggressive.
But it is the second innings where Mullanpur truly reveals its character. The dew arrives with the certainty of a sunset — from around 8:30 PM, moisture settles on the outfield and the ball, turning the surface into a chasing paradise. Bowlers who gripped the ball beautifully in the first innings find their fingers slipping. Spinners lose their turn. And the team batting second, under lights and dew, carries an advantage that the IPL has long understood but never quite solved. For two sides that both possess the batting depth to chase any total, the toss could prove to be the first tactical decision that shapes the outcome.
The boundaries are not small — square at approximately 67 metres, straight at 70 — but this is a fast outfield where well-timed shots race to the rope. For SRH's power hitters — Klaasen, Head, Abhishek — and RR's stroke-makers — Jaiswal, Sooryavanshi, Hetmyer — this surface will be familiar enough to feel comfortable and different enough from their home grounds to demand adjustment. The side that reads these conditions faster wins. In an Eliminator, there is no second innings to figure things out.
Sunrisers Hyderabad swept both league meetings against Rajasthan Royals, and the manner of those victories is instructive. In Hyderabad on April 13, SRH's bowling — led by Harshal Patel's variations and Brydon Carse's pace — restricted RR to 159 all out, with Jaiswal falling for 22 and Sooryavanshi for 11 against the new ball. The 57-run margin told the story of a side that had been outplayed in every phase. The return fixture in Jaipur was even more emphatic — but in the opposite direction of what RR had planned. Sooryavanshi scored a spectacular century for the Royals, pushing them to 229, and the match looked done. SRH chased it down with overs to spare, Abhishek Sharma and Ishan Kishan dismantling an attack that included Archer, Sandeep Sharma, and Bishnoi.
Two comprehensive wins. Two different methods. But playoff cricket is a different sport — the pressure amplifies every mistake, the margins narrow, and the team that carried form through the league does not always carry it through the knockouts. Rajasthan Royals' coaching staff, led by Kumar Sangakkara, will have studied those two defeats forensically. The question is whether the solutions they have identified — perhaps a different bowling plan for Abhishek, perhaps a modified field for Klaasen in the death overs, perhaps an adjusted batting order to counter SRH's spin in the middle — can be executed under the weight of an Eliminator, where the cost of getting it wrong is not two points but an entire season.
Riyan Parag said it plainly after the MI victory: he was not supposed to play that match. The hamstring injury that forced him to miss the LSG fixture is not fully healed, and the RR captain is managing pain rather than fitness — a distinction that matters enormously in a match where a dropped catch, a hesitation between the wickets, or an inability to dive in the field could be the difference between survival and elimination. Parag has been one of the stories of IPL 2026 — a young captain who has grown into the role with a maturity that belies his age — but an Eliminator tests not just skill and temperament but the body's willingness to perform under duress. If his movement is restricted, it affects not just his batting but his captaincy — the energy in the field, the ability to position himself at key moments, the confidence he transmits to his team.
Ravindra Jadeja's situation is similarly delicate. The all-rounder — traded from CSK to RR before this season — has been nursing knee and elbow injuries. The Royals' management has confirmed he needs at least two days of rest to be fully fit, and the gap between the MI match on May 24 and the Eliminator on May 27 gives him exactly that window. If Jadeja is fit enough to bowl his full quota and bat in the lower middle order, RR's balance changes significantly — his left-arm spin, his fielding, and his big-match experience are assets that no replacement can replicate. If he is restricted to batting only, or if his bowling is limited, Sangakkara faces a selection dilemma that has no easy answer: do you carry an unfit Jadeja for what he might contribute, or do you back a fully fit alternative like Dasun Shanaka and accept the trade-off in spin options?
The Numbers That Frame the Eliminator
| League Phase Standings | SRH: 3rd (18 pts, 9W-5L, NRR +0.524) | RR: 4th (16 pts, 8W-6L) |
| Season Head-to-Head | SRH leads 2-0 — 57-run win (Hyderabad) + chased 229 (Jaipur) |
| SRH's Last Match | Beat RCB by 55 runs (255/4 vs 200/4) — Kishan 79(46), Abhishek SR 254.55 |
| RR's Last Match | Beat MI by 30 runs — Archer removed Rohit for 0; sealed 4th-place finish on final day |
| Mullanpur This Season | Avg 1st innings: 170-180 | Highest: 254/7 (PBKS) | Dew factor significant after 8:30 PM |
| RR Fitness Concerns | Riyan Parag (hamstring) — playing despite not being fully fit; Jadeja (knee/elbow) — expected to be available |
| What's at Stake | Winner faces the loser of RCB vs GT (Qualifier 1) in Qualifier 2 at Mullanpur on May 29 |
The Playing XI Puzzle — Who Gets the Nod?
Sunrisers Hyderabad are likely to field their strongest available combination, and the good news for SRH is that their first-choice XI is largely intact. Travis Head and Abhishek Sharma should open — a partnership that, when it fires, is arguably the most destructive in the tournament. Head's ability to take on pace in the powerplay and Abhishek's capacity for innings that redefine what is achievable from an opening position give SRH a launchpad that most sides would envy. Ishan Kishan at three — in blistering form after his 79 against RCB — adds a left-handed dimension that disrupts bowling plans, while Heinrich Klaasen at four remains the most feared middle-order batter in the IPL. His strike rate against spin, his ability to clear boundaries from ball one, and his familiarity with high-pressure situations make him the player RR's bowlers will discuss most in the team meeting.
Nitish Kumar Reddy's all-round utility and Liam Livingstone's explosive finishing could provide the lower-order ballast, while Pat Cummins' captaincy and new-ball bowling anchor the attack. Harshal Patel's death-overs variations, Brydon Carse's pace and bounce, and a spin option — likely Harsh Dubey — would round out a bowling unit that has the tools for Mullanpur's conditions. SRH might consider Eshan Malinga for extra pace on a surface that rewards hitting the deck.
Rajasthan Royals' selection hinges almost entirely on fitness. If Riyan Parag and Ravindra Jadeja are both available — as expected — the XI would likely feature Yashasvi Jaiswal and Vaibhav Sooryavanshi at the top, with Lhuandre Pretorius providing the No. 3 aggression that has worked in recent matches. Parag at four, Dhruv Jurel at five, and Donovan Ferreira or Shimron Hetmyer offering the left-handed power in the middle overs — these are the batting pieces that Sangakkara will want to deploy. The bowling rests on Jofra Archer's express pace, Sandeep Sharma's new-ball swing, Sushant Mishra's left-arm variations, and the leg-spin of Ravi Bishnoi if conditions allow. If Jadeja's fitness is compromised, Dasun Shanaka offers a batting-heavy alternative with medium-pace options, though the loss of Jadeja's spin would thin the attack significantly on a surface that might offer turn before the dew settles.
The Verdict
Playoff cricket strips away the comfort of context and leaves only the question: who is better equipped, right now, for this one match? And the answer — with the usual caveat that an Eliminator is the format most likely to produce upsets — tilts towards Sunrisers Hyderabad.
The reasons are layered. SRH have the head-to-head advantage — 2-0 in the league, including a chase of 229 that demonstrated they know exactly how to dismantle this RR attack. They have the form — the 255-run demolition of RCB in their final league match was not the performance of a side winding down but of a team peaking at the right moment. They have the fitness — Cummins is back, the squad is largely healthy, and the luxury of not playing since May 22 gives them three days of rest that the Royals, who played on May 24, do not enjoy. And they have the batting firepower for Mullanpur's surface — Head, Abhishek, Kishan, and Klaasen on a pitch that rewards stroke-play is a combination that would challenge any attack in the world.
But the case for RR is not one to dismiss lightly. Jofra Archer with the new ball is capable of turning any match in the first three overs — as he did against MI, removing Rohit for a duck and setting the tone for the evening. Jaiswal and Sooryavanshi, on their day, are the most exciting opening pair in the tournament. And there is something about teams that qualify on the final day — teams that have survived the brink and emerged — that gives them a particular fearlessness. RR have nothing to lose. They were supposed to go home; they did not. That freedom can be dangerous.
The toss will matter — it always does when dew is a factor, and at Mullanpur it is a significant one. The team batting second carries an advantage that the numbers support and the eyes confirm. If SRH win the toss and bowl first, their attack has the tools to restrict and their batting has the depth to chase. If RR win the toss and bat first, the equation changes — can they post enough to defend on a surface that gets easier as the night deepens?
The lean is SRH — better form, better fitness, better season record, and a batting lineup that suits this surface. But Eliminators have a way of humbling the favourite, and Rajasthan Royals have been humbled enough this season to know that the only response to adversity is to play with the freedom of a side that has already looked defeat in the face and walked away. The margin between these two, on a neutral ground in Mullanpur, is thinner than the league table suggests. What remains is the match itself — and the match, as always, will have the final word.
The Eliminator. The most unforgiving fixture in the IPL. SRH's firepower against RR's survival instinct — who blinks first?
Our Match Analyzer has the full win probability model for this Eliminator — built on Mullanpur-specific pitch data, dew-factor trends, head-to-head records, and real-time fitness assessments. The playoffs leave no room for guesswork. Unlock your CricIntel Pro report and make sure your predictions are powered by data, not hope.
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.
- 1Heinrich KlaasenOverseasWicket-KeeperStarted last match · Top-5 batter (#3) · Automatic XI pickScore41
- 2Aniket VermaBatterStarted last match · Automatic XI pickScore18
- 3Praful HingeBatterStarted last match · Automatic XI pickScore18
- 4Travis HeadOverseasBatterStarted last match · Automatic XI pickScore18
- 5R. SmaranBatterSquad regularScore5
- 6Abhishek SharmaAll-RounderStarted last match · Top-15 batter · Automatic XI pickScore36
- 7Nitish Kumar ReddyAll-RounderStarted last match · Automatic XI pickScore18
- 8Shivang KumarAll-RounderStarted last match · Automatic XI pickScore18
- 9Eshan MalingaOverseasBowlerStarted last match · Top-15 bowler · Automatic XI pickScore32
- 10Sakib HussainBowlerStarted last match · Automatic XI pickScore18
- 11Harsh DubeyBowlerStarted last match · Automatic XI pickScore18
- 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-5 bowler (#3) · Automatic XI pickScore54
- 9Nandre BurgerOverseasBowlerStarted 2 of last 3 · Automatic XI pickScore32
- 10Ravi BishnoiBowlerStarted 2 of last 3 · Automatic XI pickScore32
- 11Sandeep SharmaBowlerStarted 2 of last 3 · Automatic XI pickScore32
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.