NEWGet Rs 100 welcome bonus - code CRICNINJA100
Download App

Rajasthan Royals vs Sunrisers Hyderabad IPL 2026 Match 36 Fantasy Preview at Sawai Mansingh Stadium: Captain Picks, Predicted XIs and SMS Pitch Notes

A retrospective fantasy read on IPL 2026 Match 36 between Rajasthan Royals and Sunrisers Hyderabad, scheduled for Saturday 25 April 2026 at 7:30 PM IST at Sawai Mansingh Stadium, Jaipur. The notes below restate the predicted XIs, captain lanes, SMS surface cues and Jaipur weather context that the original CricTracker Dream11 preview, published at 7:15 PM IST on the same day, used to frame the fixture before the toss.

Evening cricket stadium atmosphere under floodlights at a Jaipur IPL fixture, with stands filling and a dry warm playing surface in the centre

· CricNinja News Desk · Retrospective fantasy brief

Compliance notice: CricNinja is a skill-based fantasy sports platform for users 18+ in permitted Indian states. Fantasy outcomes depend on real match performance. Predicted XIs and captain notes below reflect the preview published on the original date, not post-toss confirmations. Coverage is intended for free fantasy contests and is consistent with the Indian Government's Gaming Regulation Bill, 2025.

IPL 2026 Match 36 was scheduled for Saturday 25 April 2026, first ball 7:30 PM IST at Sawai Mansingh Stadium in Jaipur, broadcast on Star Sports Network and streamed on JioHotstar. CricTracker published a Dream11 fantasy preview at 7:15 PM IST on the same day, framing the fixture as a form-and-venue intersection: a Rajasthan Royals side coming off a 40-run win against Lucknow Super Giants, and a Sunrisers Hyderabad side arriving on a 47-run win over Delhi Capitals that featured a 135 off 68 from Abhishek Sharma. Read now as a dated archive rather than a live lock-in sheet, that brief still maps the role lanes that mattered for captain selection, impact-player swing and the SMS surface behaviour that tends to favour a specific bowling shape.

The framing here is narrower than a recap. It is a record of what the preview published, what role map the predicted elevens implied, and how the SMS surface cue fed back into captain choice. The numbers, names and form lines below are taken from that CricTracker brief alone. Anything that requires post-toss confirmation, ball-by-ball scoring or final ownership splits is deliberately left out.

Fixture

Sawai Mansingh Stadium, Jaipur · 25 April 2026 · 7:30 PM IST · IPL 2026 Match 36

RR form (last 5)

W, L, L, W, W. Last result: 40-run win over Lucknow Super Giants.

SRH form (last 5)

W, W, W, L, L. Last result: 47-run win over Delhi Capitals.

Jaipur weather

About 32.7°C, 55% humidity, rain forecast at preview time.

How the form run fed the captain lanes

Rajasthan Royals arrived on a WLLWW sequence, fresh from a 40-run win over Lucknow Super Giants in which Yashasvi Jaiswal made 22, Ravindra Jadeja hit 43, Jofra Archer took 3 for 20, and Nandre Burger plus Brijesh Singh each picked up two wickets. That mix told a useful story for fantasy rooms: the Royals did not win on one dominant batting burst, they won on a four-pronged effort spread across top order, middle overs and the powerplay seam overs. Jaiswal's contribution was modest; Jadeja's contribution was the bridge; Archer and Burger closed on the ball.

Sunrisers Hyderabad arrived on a WWWLL sequence and had just beaten Delhi Capitals by 47 runs. The headline of that game was Abhishek Sharma's 135 off 68 balls, with Heinrich Klaasen adding 37 off 13, Eshan Malinga taking 4 for 32, and Harsh Dubey taking three wickets. The shape there was almost the inverse of the Royals win: a single batter carried the bulk of the run volume, and the bowling split the wickets across two names rather than four. For fantasy rooms, the SRH read was a high-ceiling batter plus a defined pace-spin pair, the RR read was a balanced unit with two seam lanes and a middle-overs anchor.

Close cricket editorial frame of a top-order batter playing a cover drive at a Jaipur evening match, with shallow depth of field
Captain value on a balanced SMS surface sat with batters who combined top-order volume with a defined role in the chase, not with the headline run scorers alone.

Predicted RR XI and the role splits

The CricTracker brief listed the probable Rajasthan Royals XI as V Suyavanshi, Yashasvi Jaiswal, DC Jurel as wicketkeeper, R Parag as captain, Shimron Hetmyer, D Ferreira, RA Jadeja, Jofra Archer, N Burger, Ravi Bishnoi and B Sharma. That is a twelve-name field, with impact player still to be named. Read by role, the sheet splits cleanly: Suyavanshi and Jaiswal share the new-ball overs at the top of the order; Parag is the organising captain who can also give a few overs of spin; Jurel is the gloves path and therefore the dual-scoring keeper-batter; Hetmyer and Ferreira fill the middle-order finishing lanes; Jadeja is the middle-overs all-rounder who also controls left-arm spin; Archer and Burger are the two seam quicks who exploit any movement; Bishnoi is the wrist-spin control option; B Sharma is the third seamer or bowling all-rounder in the named XI.

For fantasy construction, the Royals sheet offered two premium captain lanes (Jaiswal as top-order volume, Jadeja as all-rounder with full quota), a captain anchor (Parag), a keeper dual path (Jurel), a wrist-spin differential (Bishnoi), and two seam quicks who shared new-ball licence on an SMS surface known for early movement. The Royals did not need every name on a single card; they needed three or four well-mapped roles and the freedom to leave the rest to lower-leverage picks.

Predicted SRH XI and the differentials that mattered

The probable Sunrisers Hyderabad XI in the same preview read: Abhishek Sharma, TM Head, Ishan Kishan as captain, H Klaasen as wicketkeeper, Salil Arora, A Verma, K Nitish Kumar Reddy, S Kumar, Harsh Dubey, Eshan Malinga and Sakib Hussain. That twelve names a different kind of structure. Abhishek Sharma is the high-ceiling powerplay batter whose 135 against Delhi was the form headline; Head is the experienced overseas anchor at the top; Ishan Kishan, named as captain, carries the gloves-adjacent leadership role but is positioned in the order as a top-order batter rather than as a specialist keeper; Klaasen is the wicketkeeper and the middle-overs power batter, which on most Indian apps is the cleanest dual-scoring option in the side; Salil Arora and A Verma fill the middle-order and seam-bowling all-rounder lanes; Nitish Kumar Reddy is the seam-bowling all-rounder who can hold a quota; S Kumar and Harsh Dubey fill the spin-bowling lanes with Eshan Malinga and Sakib Hussain the new-ball and death-overs seam pair.

The fantasy hinge on the SRH sheet is Klaasen. A named keeper who also anchors the middle overs is rare, and on an SMS surface where the ball tends to slow in the second half of the innings his boundary range makes him a natural captain swing for rooms that want a keeper dual path instead of a pure top-order multiplier. Ishan Kishan as captain is a different kind of pick: a leadership tag that costs salary but only pays if the batting position is confirmed at the toss. The Abhishek Sharma lane is the form ceiling: high ownership in most books, but a single-player captain multiplier that does not survive a quiet powerplay.

What the SMS surface note did to the build

Sawai Mansingh Stadium was described in the brief as a balanced surface with relatively large straight boundaries, grip for spinners in the middle overs, new-ball movement for pacers, an average first-innings score of about 167, and an even 50% pace versus spin split. That combination is not a flat track, it is not a square turner, and it is not a green seamer. It is a venue where both phases of the innings have a defined edge: the powerplay belongs to the seamers who find movement, the middle overs belong to the spinners who find grip, and the death overs belong to the batters who can clear the long straight boundaries under pressure.

That surface note changes two fantasy decisions. First, the captain tag should not sit by default on a powerplay-only batter: on an SMS night the second-innings middle overs can be more valuable than the first-innings powerplay if the chase is in range. Second, the bowling slots should not be flooded with pace: a wrist-spin option that earns four overs of grip is worth at least one of the three bowling slots. Pure finishers who face only a handful of balls at the death become lower-priority spends unless they also bowl, because the long straight boundaries compress their ceiling.

Tactical cricket field setup during the middle overs at a Jaipur evening match, with spinners operating into a defined grip surface
On an SMS night with grip in the middle overs, one wrist-spin slot returned more than a fourth seamer.

Jaipur weather and what the rain forecast implied

Jaipur at preview time was reported at 32.7°C with 55% humidity and a rain forecast. Warm, slightly humid evenings at SMS tend to do two things to fantasy rooms. They favour batters who clear the long straight boundaries when the ball skids on under lights, and they compress the value of new-ball swing because the ball does not hold its seam as long as it would on a cooler night. The rain forecast is the larger unknown: a shortened chase can turn a balanced pitch read into a three-bowler full-quota contest, which pushes the captain tag towards an all-rounder with bat and ball responsibility rather than a top-order batter.

None of that required a rewrite of the predicted XIs. It did require a tweak in salary allocation. A four-over wrist-spinner becomes a non-negotiable. An all-rounder who bowls a full quota becomes the cleanest captain lane. A pure-batter captain becomes the differential rather than the core. The Jaipur weather and the SMS pitch note therefore reinforced each other, which is the kind of cross-confirmation fantasy rooms tend to underweight.

DecisionPrimary namesEditorial read
RR captain anchorsYashasvi Jaiswal, Ravindra JadejaTop-order volume versus middle-overs all-rounder on a balanced SMS surface
SRH captain swingsAbhishek Sharma, Heinrich KlaasenForm ceiling from Delhi game versus keeper dual pathway in the middle overs
Keeper dual pathDC Jurel (RR), Heinrich Klaasen (SRH)Only confirmed keeper options in the named XIs; Klaasen is the higher-ceiling swing
New-ball paceJofra Archer, Nandre Burger, Eshan Malinga, Sakib HussainEarly movement noted for SMS; seam lanes shared across both sides
Wrist-spin laneRavi Bishnoi (RR), Harsh Dubey (SRH)Grip in the middle overs was the SMS-specific cue
Captain pick in the original briefYashasvi Jaiswal (C), Abhishek Sharma (VC)Top-order volume captain plus form-ceiling vice captain; Klaasen not in the named captain pair

The two captain lanes the brief actually published

The original CricTracker preview named Yashasvi Jaiswal as captain pick, with the supporting stat of 365 runs at a strike rate of 163 across his last 10 games. Abhishek Sharma was named as vice-captain, with 448 runs in his last 10 games and a 135 in the immediately prior fixture against Delhi Capitals. That captain pair is a coherent read once the role splits are applied. Jaiswal offers top-order volume on a balanced SMS surface where the powerplay still belongs to the batter who finds early movement. Sharma offers form-ceiling at a venue where the long straight boundaries reward boundary-hitters in the second half of the innings.

Neither pick should be copied as a permanent rule for SMS nights. The brief's stat lines were a snapshot of a particular form window and a particular venue read. What still travels is the construction logic behind the picks: a top-order volume captain, a form-ceiling vice captain, one all-rounder with full bowling quota, one wrist-spin option, and the freedom to leave impact-player slots under-priced until the toss card confirms them.

What this brief left open, and what it did not

The CricTracker preview established a clear baseline. The fixture was scheduled for SMS at 7:30 PM IST. Both sides had a specific form line behind them. The pitch was described as balanced with grip and new-ball movement. Weather was warm with a rain forecast. Both predicted XIs were named with role splits that mapped cleanly onto fantasy builds. The brief named one captain pick, one vice-captain pick, and the supporting stats that justified each.

The preview did not establish, and this retrospective does not invent, the post-toss XIs, the final scoreline, the public ownership percentages on Dream11 or any other platform, the actual captain multiplier outcome, or any specific ball-by-ball moment from the night itself. Those facts require a finished match report. Stick to the role map the predicted elevens and the SMS surface note actually support, and treat the toss card as the real lock whenever a similar balanced Jaipur surface appears again later in the season.

Readers building context for other IPL fantasy locks can browse more captain lanes, pitch notes and match-day fantasy briefs on CricNinja, where the same role-first method is applied across other venues and seasons.

Legacy for later SMS nights and balanced form sheets

Read from the archive forward, Match 36 of IPL 2026 still leaves a usable template. On an SMS surface that is balanced rather than flat, with grip for spinners and new-ball movement for pacers, the captain tag belongs to a batter with a defined role in both halves of the innings. A keeper dual pathway is a real swing rather than a niche pick. One wrist-spin slot belongs in the bowling core. The impact-player cards stay under-priced until the toss card confirms them. Form lines from the previous fixture are useful colour, not a captain instruction.

The next confirmed SMS date on the IPL 2026 calendar, after the original 25 April 2026 fixture, would be the Royals' next scheduled home game at the venue. Until that card is published, the construction rules above are the part of this 25 April 2026 preview that continues to travel.

← More comparisons Download CricNinja App

Use code CRICNINJA100 for your Rs 100 welcome bonus

Lowest minimum deposit. 1x wagering. Fast UPI withdrawals where permitted.

CRICNINJA100

Frequently asked questions

When and where was RR vs SRH IPL 2026 Match 36 scheduled?
IPL 2026 Match 36 between Rajasthan Royals and Sunrisers Hyderabad was scheduled for Saturday 25 April 2026 at Sawai Mansingh Stadium, Jaipur, with first ball at 7:30 PM IST. Broadcast was on Star Sports Network and streaming on JioHotstar.
What form line did each side bring into the fixture?
Rajasthan Royals arrived on a WLLWW sequence after a 40-run win over Lucknow Super Giants. Sunrisers Hyderabad arrived on a WWWLL sequence after a 47-run win over Delhi Capitals in which Abhishek Sharma hit 135 off 68 balls.
What did the Sawai Mansingh Stadium pitch note say for fantasy builds?
The CricTracker preview described SMS as a balanced surface with relatively large straight boundaries, grip for spinners in the middle overs, new-ball movement for pacers, an average first-innings score of about 167, and an even 50% pace versus spin split. That points to one wrist-spin slot, two seam lanes, and a captain with a defined role in both halves of the innings.
Who were the named captain and vice captain in the original brief?
The original preview named Yashasvi Jaiswal as captain pick with 365 runs at strike rate 163 across his last 10 games, and Abhishek Sharma as vice captain with 448 runs in his last 10 games and a 135 in the previous Delhi fixture.
What were the predicted playing XIs?
Predicted RR XI: V Suryavanshi, Yashasvi Jaiswal, DC Jurel (wk), R Parag (C), Shimron Hetmyer, D Ferreira, RA Jadeja, Jofra Archer, N Burger, Ravi Bishnoi, B Sharma. Predicted SRH XI: Abhishek Sharma, TM Head, Ishan Kishan (C), H Klaasen (wk), Salil Arora, A Verma, K Nitish Kumar Reddy, S Kumar, Harsh Dubey, Eshan Malinga, Sakib Hussain.
What is the practical takeaway from this retrospective brief?
On a balanced SMS surface with grip in the middle overs and new-ball movement, put the captain tag on a top-order volume batter or a middle-overs all-rounder, keep one wrist-spin slot, protect two seam lanes, and wait for the toss before spending salary on impact players. Predicted XIs are scaffolding; the toss card is the lock.