On Sunday, 3 May 2026 at 7:30 PM IST, Gujarat Titans hosted Punjab Kings in IPL 2026 Match 46 at the Narendra Modi Stadium in Ahmedabad. The CricTracker Dream11 preview that morning ran on a captaincy frame, pitting Shubman Gill against Shreyas Iyer as the headline duel. Read three months later, the underweighted axis inside that same preview was the wicketkeeper slot. Jos Buttler sat at three for Gujarat Titans with a 39 from the previous fixture, and Prabhsimran Singh opened for Punjab Kings with a 59 from their previous fixture. Both keepers were listed in the probable XIs. Both were drafted as overseas or top-order points paths, not as captaincy candidates. The retrospective read on that preview is below: how the wicketkeeper differential moved between fixtures, where the Buttler vs Prabhsimran call sat inside the form windows, and which parts of the keeper-first read aged well across the rest of the season.
Why the keeper slot moved more than the captain slot between fixtures
The preview's opening frame was the captaincy frame, and that frame was correct as far as it went. Gill had scored 43 in Gujarat Titans' previous match, a 4-wicket win over Royal Challengers Bengaluru chasing 155 in 15.5 overs. Iyer had lost the previous match, a 6-wicket loss to Rajasthan Royals after Punjab Kings posted 223. The captaincy frame on the morning of 3 May pointed at Gill, because form pointed at Gill and the chasing frame pointed at Gill. Where that frame underweighted a separate axis was the wicketkeeper slot. Buttler's 39 against RCB came at a strike rate above 150, with a boundary-strike ceiling higher than Gill's anchor 43 in the same chase. Prabhsimran Singh's 59 against RR came at the top of the order on a flat deck, with a boundary-strike rate higher than Iyer's middle-overs rebuild in the same match. Both keepers carried points ceilings the captain frame did not surface.
The reason the keeper slot moved more between fixtures than the captain slot is structural. Captain runs are anchored to the role: the captain bats first, faces the toughest overs, holds the innings together. Keeper runs are anchored to the batting position plus a secondary skill: stumpings, catches behind the stumps, and a boundary-strike role that compounds when the batter in front of them gets out early. On a chasing deck, the keeper's batting position compounds because the keeper reaches the crease inside the powerplay. On a flat batting deck, the keeper's catching role compounds because more edges carry. The preview did not name that axis. The preview's probable XIs carried it anyway, in the names listed at three for Gujarat Titans and at the top for Punjab Kings.
What the form windows said about each keeper's ceiling
The form window on the morning of 3 May was unusually informative. Gujarat Titans sat at W W L L W across the previous five matches. Punjab Kings sat at L W W W W across the same window. Reading the keeper slots through that window, Buttler's ceiling was a 30-to-50 anchor innings with a wicketkeeping points layer underneath, on the side that had just chased 155 with the top order firing. Prabhsimran Singh's ceiling was a 50-to-70 attacking innings on a flat deck, with a wicketkeeping points layer underneath, on the side that had just lost despite posting 223. The form window pointed at Buttler on ceiling reliability and at Prabhsimran on ceiling magnitude. The two ceilings are different. The retrospective question is which ceiling aged better.
Reading the same window through the lens of the chase-bias Ahmedabad surface, the answer tilts toward Buttler. A 178 first-innings average on a chase-bias deck is a 55-45 chase regardless of which side bats first. In a chase, the keeper who bats at three reaches the crease before the seventh over and finishes the innings inside twenty overs. In a chase, the keeper who opens reaches the crease inside the second over and finishes the innings earlier still, but with a higher variance ceiling. The form window that produced a 39 from Buttler and a 59 from Prabhsimran pointed at a higher floor for Buttler and a higher ceiling for Prabhsimran. The preview's published probable XIs reflected both readings without naming either.
How the probable XIs stacked the keeper against the captain
The probable Titans XI read: Shubman Gill (C), Sai Sudharsan, Jos Buttler (wk), Washington Sundar, Shahrukh Khan, Jason Holder, Rahul Tewatia, Arshad Khan, Rashid Khan, Kagiso Rabada, Prasidh Krishna. Buttler sat at three with the overseas wicketkeeper tag. The probable Kings XI read: Priyansh Arya, Prabhsimran Singh (wk), Cooper Connolly, Shreyas Iyer (C), Nehal Wadhera, Marcus Stoinis, Shashank Singh, Marco Jansen, Arshdeep Singh, Yuzvendra Chahal, Lockie Ferguson. Prabhsimran sat at two with the Indian wicketkeeper tag and the opening role.
Reading the two XIs side by side, the keeper slot stacked against the captain slot in a specific way. Gill captained from the top of the order with the chasing frame behind him; Buttler came in at three with the overseas middle-order role. Iyer captained from four with the rebuilding frame behind him; Prabhsimran opened with the attacking frame in front of him. On a chase-bias deck with a 178 first-innings average, the keepers reached the crease at different phases of the innings. Buttler reached the crease after the powerplay, with the chase set up. Prabhsimran reached the crease inside the powerplay, with the chase to build. The two roles produced different points ceilings on the same deck. The preview did not call the difference out. The probable XIs carried it.
Reading the credit math on each probable XI added a second layer. On the Titans side, Gill, Buttler, Rabada, and Rashid Khan carried the bulk of the overseas credit, with Sai Sudharsan, Washington Sundar, Holder, and Prasidh Krishna in the middle band. Buttler's points per credit sat higher than Gill's on the same probable XI, because Buttler's boundary-strike role compounded with the chasing frame in a way the captain role did not. On the Kings side, Connolly, Stoinis, Jansen, and Ferguson carried the overseas credit, with Prabhsimran, Iyer, Arshdeep, and Chahal in the middle band. Prabhsimran's points per credit sat higher than Iyer's on the same probable XI, because Prabhsimran's opening-role ceiling compounded with the attacking frame in a way the captain role did not. The retrospective read on that credit math is that the keeper slot on each XI carried more differential value than the captain slot on the same XI.
Why the Ahmedabad surface shifted the keeper call sideways
The preview's pitch report described the Narendra Modi Stadium surface as traditionally batting-friendly with a quick outfield, early new-ball movement possible, and an average first-innings score around 178. The toss expectation in the preview was that captains would bowl first on winning the toss, citing the chase-bias history at the venue. That frame held. What it did to the keeper call was move it sideways: the keeper call became a function of which side won the toss and bowled first, because the chasing keeper reaches the crease at a different phase of the innings than the setting keeper.
Reading the surface through the keeper slots, the sideways shift is the operative line. On a flat Ahmedabad deck, Buttler's boundary-strike role compounds in the middle overs, when the older ball sits up on a length and the chasing side is willing to take risks. On the same flat deck, Prabhsimran's boundary-strike role compounds in the powerplay, when the new ball moves enough for the bowlers to miss their lines and the attacking side is willing to go over the top. The two roles suit different innings phases. The preview's pitch report did not name either role. The probable XIs listed both keepers in roles that pointed at the different phases, and the chase-bias expectation in the same preview told readers to weight the second-innings role more heavily.
The bowling reads the preview kept visible around the keeper axis
The preview did not run on the keeper axis alone. It ran on a bowling axis too, and that axis sat visibly around the keeper call. The bowling reads were a four-pronged seam attack for the Titans (Arshad Khan, Holder, Rabada, Prasidh Krishna) and a four-pronged bowling unit for the Kings (Arshdeep, Chahal, Jansen, Ferguson). The keeper call sat inside the bowling reads, because a wicketkeeper's catching points compound when more bowlers are taking wickets. On the Titans side, four bowlers generating ten or more wickets in a chasing frame produced a high keeper catch ceiling. On the Kings side, four bowlers generating ten or more wickets in a setting frame produced a similar ceiling. The keeper call was therefore a function of the bowling reads, not a separate axis.
Reading the bowling axis through the keeper slots on the morning of 3 May, the differential sat on the Titans side. Arshad Khan had returned 3 for 22 in 3.2 overs against RCB. Holder and Rashid Khan had taken two wickets each. The total wicket-taking paths on the Titans side were five, with four named bowlers sharing the workload. The total wicket-taking paths on the Kings side were four, with three named bowlers sharing the workload. The keeper call sat on the side with more wicket-taking paths, because more wickets means more catches. The retrospective read on that math is that the keeper call and the bowling call pointed the same direction.
Weather, dew and the keeper's second-innings ceiling
The preview listed weather at 26.0 degrees Celsius with 78 percent humidity and noted the broadcast was on Star Sports Network with live stream on JioHotstar. The weather note did useful work for the keeper call. Humidity around 78 percent in Ahmedabad in early May is high enough that dew is a real second-innings factor. A wet ball in the second innings is harder for the bowlers to grip, harder for the spinners to turn, and easier for the batters to score against. The keeper's keeping points in the second innings are therefore higher than in the first, because more edges carry when the ball is wet.
Reading the dew note through the keeper slots, the second-innings keeper call carried a higher ceiling than the first-innings keeper call on a humid Ahmedabad evening. Buttler's second-innings ceiling on a wet ball, behind a four-pronged Titans attack, was the higher of the two ceilings named in the preview. Prabhsimran's second-innings ceiling, in front of a four-pronged Kings attack, was lower on the same calculation. The dew note tilted the keeper call back to the Titans side, in a way the form window and the credit math had not. The preview did not draw the line. The weather note in the same preview carried the line implicitly.
Broadcast, late changes and the keeper call after toss
The preview's broadcast pointer was useful as a verification check, in the same way it is for every other slot. The keeper call after toss depended on two pieces of information the preview could not lock in advance: the confirmed playing XI, and the toss decision. Both are visible on the Star Sports broadcast from about 7:00 PM IST on match day. If the toss winner bowled first, the keeper call moved to the chasing side. If the toss winner batted first, the keeper call moved to the setting side. The vice-captain hedge on the keeper slot was the single most important line in the preview's late-change workflow, because the keeper ceiling was the highest points ceiling on each XI after the captain.
Reading the late-change workflow through the keeper slots, the verification check reduced to three named sources. The operator's official social channel, the league's published squad announcement, and the toss-time update from the venue. The preview's probable XIs were probable, not confirmed. The keeper call on the morning of 3 May was the highest-ceiling call on each XI conditional on the XI being confirmed. The retrospective read on that workflow is the same as the workflow itself: verify the XI on two of three sources before locking the squad, and recheck the keeper call once the toss confirms the order.
The differential slots that fell out of the keeper-first read
The differential slots that fell out of a keeper-first reading of the preview were four. On the Titans side, Buttler was the differential overseas wicketkeeper, with a boundary-strike ceiling higher than the captain's anchor ceiling. Arshad Khan was the differential new-ball seamer, with the 3 for 22 against RCB and a workload path on a chase-bias deck. On the Kings side, Prabhsimran was the differential Indian wicketkeeper, with an attacking ceiling higher than the captain's rebuilding ceiling. Marco Jansen was the differential seam-bowling all-rounder, with a powerplay bowling workload and a small batting path. Each of those four slots carried a workload hedge that did not depend on the toss outcome.
Reading those four differentials against the credit math on each probable XI, the keeper-first read was the strongest of the four. Buttler's points per credit on the Titans probable XI was higher than Arshad Khan's, because Buttler's batting role compounds in a way a pure bowling role does not. Prabhsimran's points per credit on the Kings probable XI was higher than Jansen's, because Prabhsimran's batting role compounds in a way a pure all-rounder role does not. The retrospective read on those credit ratios is that the keeper-first differential was the strongest call the preview's probable XIs made available, sitting under the captain frame the preview led with.
What the keeper math says about the rest of the season
Three months after the 3 May preview was published, the keeper-first read on that fixture holds up. Buttler's middle-overs role on a chase-bias Ahmedabad deck, behind a four-pronged Titans attack with a wet second-innings ball, is the operational frame for any fixture where an overseas wicketkeeper sits at three on a chasing side. Prabhsimran's opening-role ceiling on a flat deck, in front of a four-pronged Kings attack with a setting frame, is the operational frame for any fixture where an Indian wicketkeeper opens on a flat batting surface. The two roles suit different phases of the same innings. The preview's probable XIs carried both. The keeper-first retrospective on that preview is the strongest single axis the same preview made available under the captain frame it ran on.
For fantasy pickers reading the retrospective on 3 May, the operational lesson is the axis itself. When a Dream11 preview leads with a captaincy duel, check the wicketkeeper slots on each probable XI before locking the captain. The captain call is the highest-ownership call on the card. The keeper call is the highest-ceiling call. On a chase-bias deck with a wet second-innings ball, the keeper on the chasing side compounds in a way the captain does not. On a flat batting deck with a setting frame, the keeper on the setting side carries a different ceiling still. The preview's probable XIs carried both ceilings. The retrospective finds them three months later. Read the next match preview on the fantasy cricket news desk for the same axis on the next fixture.