On the evening of 9 April 2025, IPL 2025 Match 23 between Gujarat Titans and Rajasthan Royals was less a contest between two settled XIs than a contest between two paper depth charts and the bowlers who actually turned up at the Narendra Modi Stadium. The form table said one thing. The injury room said another. The fantasy math on the morning of the match was forced to reconcile both, and the bowler split that came out of that reconciliation is the part of the night that still carries into every flat-track IPL fixture where a franchise loses two seamers to factors outside the playing squad's control.
Gujarat Titans arrived for the fixture second on the points table with three wins from four matches. Rajasthan Royals were seventh with two wins and two losses. The Royals were a more settled batting unit — Sanju Samson, Dhruv Jurel, Riyan Parag and Nitish Rana were all striking above 150 going in, with Rana's rate above 180. The Titans had a form opener in Shubman Gill and a four-match winning run under his captaincy. The pitch was the same Narendra Modi deck that had produced 243, 232, 196 and 160 in the four completed innings before that night, which is a surface that punishes bowlers who miss their lengths. None of that was the controlling variable on 9 April. The controlling variable was the seam-bowling depth chart, which had collapsed in two specific places: the left-arm quick that the Titans expected to have in the squad, and the right-arm veteran they had originally signed for exactly this kind of fixture.
The two names that left before the toss
Gerald Coetzee did not play the 9 April fixture because of the hamstring strain that had already kept him out of the Champions Trophy after SA20. The same muscle group. The same rehab timeline. By the time the Titans named their playing XI on the evening of the match, the franchise had effectively run out of patience on a return date and named him out of the squad. Coetzee had been the planned third seamer — the new-ball alternative to Mohammed Siraj, the bowler who was meant to give the Titans two distinct pace looks in the powerplay. Without him, the third-seam option was Prasidh Krishna on his day, which is a different profile: less new-ball threat, more length and slower-ball variety in the middle phase.
The other absence was Kagiso Rabada. Rabada had departed for personal reasons during the season, and the Titans' bowling depth chart had been rebuilt around his return. The plan was Siraj and Rabada at the top, with Coetzee as the third seamer and Sai Kishore as the left-arm spin control. The reality on 9 April was Siraj, Sai Kishore, and a choice between Prasidh Krishna and Ishant Sharma as the third-seam backup. Ishant had leaked 12 runs per over across three games with one wicket to show for it. The fantasy math had already demoted him from the captaincy conversation. The math now had to decide whether to demote him from the playing XI entirely.
What the three-seamer build actually did to the fantasy math
The bowler split on the morning of 9 April looked like this. From the Titans side, the wicket-taking core was Mohammed Siraj and R Sai Kishore. Siraj had been the leading new-ball wicket-taker for the Titans in the four completed matches to that point, and Sai Kishore was the left-arm spin match-up against a Royals order that ran right-handers at positions three, four and five. The third seamer slot went to Prasidh Krishna on the published fantasy team — the conservative call, because Prasidh had the best length-control numbers in the squad in the preceding two matches. Ishant Sharma stayed in the conversation as a differential only, with the bench tag explicit on most published fantasy teams. From the Royals side, Jofra Archer was the single mandatory death-overs pick, and Maheesh Theekshana was listed in the predicted XI as the spin partner if the franchise went with two frontline tweakers.
What the three-seamer build did to the fantasy math was compress the wicket-taking ceiling for the Titans. With Siraj and Sai Kishore as the only confirmed wicket-takers in the attack, the probability of a multi-wicket over from the Titans bowling unit dropped. That compression forced the captaincy conversation toward the top of the order — the side that was going to take wickets in this fixture was the Royals, which meant the captain armband belonged to the batter most likely to face the Royals bowlers, not the bowler most likely to take Royals wickets. The captaincy math that flowed from the depth chart was the same conclusion the morning fantasy team had already drawn: Gill was captain, Samson was vice-captain. The depth chart explained the math; it did not invent it.
Why Rashid Khan was kept off the captain armband despite the surface
The Narendra Modi surface on 9 April was the kind of deck that, in any normal season, would have made Rashid Khan the captaincy pick. The previous four completed innings had produced 243, 232, 196 and 160. Three of those totals were over 195. The chasing side had won three of the four. The dew reading on the morning of the match was heavy. On a flat deck with heavy dew and a successful chase pattern, a finger-spinner who can take wickets in the powerplay is the captaincy pick on most nights. Rashid is that spinner. He is the highest-ceiling bowler in the league in almost any match context.
What kept Rashid off the captain armband on 9 April was a number. He had managed one wicket in four matches and was conceding over 10 runs per over. That is the worst IPL start of his career, and the fantasy math on a flat deck reads that record literally. The captain multiplier rewards ceiling, and ceiling collapses when the bowler's economy is in double digits and the wicket count is at one. The model kept Rashid as a regular XI pick — his ceiling is high enough that any given over can swing 30 fantasy points in either direction — but it refused to put the armband on him. The risk-adjusted ceiling on Rashid on 9 April was lower than the risk-adjusted ceiling on Gill, and the fantasy team honoured the math.
The wrinkle inside the wrinkle was that the surface was exactly the kind that would have rewarded Rashid if he had found his rhythm. The dew, the chase pattern, the flat deck, the right-hand-heavy Royals middle order — all of it pointed to a wicket-taking ceiling on Rashid. The model acknowledged that ceiling in the regular XI pick. The model refused to fund it at captaincy. That distinction is the kind of decision a fantasy manager has to make with their head, not their heart, and the published team on the morning of the match was explicit about it: Rashid in, armband off.
The Royals batting order and what the bowler split meant for them
The Royals' batting card on 9 April was the most settled part of the night. Samson, Jurel, Parag and Rana were the power-hitting core. Yashasvi Jaiswal was the form opener at the top, with 101 runs in four innings and a strike rate of 131.16, with 67 of those runs coming in a single knock against Punjab Kings. Shimron Hetmyer was the middle-overs accelerator. The published fantasy team took Jaiswal as a regular XI pick rather than a captaincy slot, on the basis that the three-seamer build pointed toward a chase scenario where the Royals' openers would bat twice and the Titans' openers would bat once. Jaiswal's floor in that scenario was high enough to justify the slot, but his ceiling was conditional on a long powerplay.
The bowler split on the Royals side was the inverse of the Titans' problem. Archer was the single highest-floor death bowler in the league on 9 April. Theekshana gave the Royals a spin match-up against the Titans' left-hand top order if Sai Sudharsan came in early. Sandeep Sharma was the new-ball partner. The Royals did not have a depth-chart collapse. They had a settled three-phase plan: new ball, middle overs, death. The Titans had a collapse: new ball, one seamer, one spinner, one backup seamer on a strict length-control brief. The fantasy math on the morning of the match was built around that asymmetry. The published captain pick (Gill) and vice-captain pick (Samson) were both bets on the team with the more settled plan batting second in a chase scenario that favoured the team with the more settled plan.
Where the published Dream11 team landed and why
The published Dream11 selection on the morning of 9 April read: wicketkeepers Sanju Samson and Jos Buttler; batters Yashasvi Jaiswal, Riyan Parag, Shubman Gill and B Sai Sudharsan; all-rounders Nitish Rana and Wanindu Hasaranga; bowlers Jofra Archer, R Sai Kishore and Mohammed Siraj. Captain Shubman Gill. Vice-captain Sanju Samson. The bowler split inside that XI is the key record. Three frontline bowlers: Archer from the Royals, Sai Kishore and Siraj from the Titans. Three all-rounders who could bowl if needed: Hasaranga, Rana, and (on some squads) Washington Sundar. The depth chart on the Titans side said the franchise was going to lean on Siraj and Sai Kishore to take 10 wickets between them. The fantasy XI funded that bet by giving both the slot and trusting the rest of the wicket-taking load to Archer from the Royals side.
The differential pick on the morning of the match was Sai Sudharsan. Sai Sudharsan had been a quiet presence in the Titans' middle order through the first four matches, and his inclusion in the published XI was a function of the Royals' left-arm spin options. If the Royals went with Theekshana and one of the Indian spinners, Sai Sudharsan's right-handed sweep was the match-up. The published team took the bet. The differential was small — Sai Sudharsan was the third-most-owned batter on the published card — but it was there.
What the depth chart taught fantasy managers about every future fixture
Two structural lessons from 9 April 2025 still carry. First, when a franchise loses two seamers in a single build cycle — one to injury, one to personal absence — the fantasy bowler split does not default to the next-in-line seamer. It defaults to the spinner and the one remaining specialist, and the third seamer slot becomes a length-control brief rather than a wicket-taking brief. The published team on 9 April handled this by taking Siraj and Sai Kishore and giving Prasidh Krishna the third slot on length numbers, not wicket numbers. That split would have looked strange on a normal night. On a night with a depleted pace attack, it was the only honest split.
Second, the captaincy math on a flat deck with a depleted bowling attack flows away from the obvious spinner and toward the form batter who will bat second. The form batter on 9 April was Gill. The form batter on the Royals side was Samson. The published team captained Gill and vice-captained Samson. That decision is what the depth chart asked for, and the depth chart asked for it because the Titans' bowling attack could not promise enough wickets to make Rashid's ceiling worth the captain multiplier. The same logic applies in every fixture where a franchise loses a strike bowler on the morning of a chase-friendly surface. Captain the form batter who bats second. Leave the spinner on the bench of the captaincy conversation until the economy number resets.
The 9 April fixture is now part of the fantasy archive. The bowler split, the captaincy call and the depth-chart reasoning are the parts of the night that survive the post-match scorecard. The pitch, the dew and the chase pattern were the variables on the night. The two absences — Coetzee and Rabada — were the variables before the night. The published fantasy team on 9 April was built around both, and the bowler split inside the XI is the structural record that a fantasy manager can take into the next flat-track IPL fixture where a franchise shows up with one fewer seamer than the depth chart promised.
For the broader News desk archive, see Blog Daily Archive.