Home · Teams · Gujarat Titans
Franchise desk · GT

Gujarat Titans — Ahmedabad flat track, Shubman Gill's batting captaincy, and the Rashid wicket-taking matrix

GT is built around the flattest deck in the league. The Narendra Modi Stadium in Ahmedabad produces totals in the 200-plus range most nights and rewards the batters who take the initiative through the powerplay. Shubman Gill leads the side with a top-order batting brief; Rashid Khan is the wicket-taking anchor in the middle overs. Sai Sudharsan and Jos Buttler fill the top-order slots that make GT's batting the deepest in the league.

Editorial view of the Narendra Modi Stadium in Ahmedabad — GT's home venue during an IPL 2026 match.
Independent editorialNo operator ties
Free to readNo subscription, no app
Updated continuouslyToss to post-match
Responsible framingSkill game, real money, real risk
Squad structure

What the GT squad looks like in 2026

Batting

Top-order and middle-order

Sai Sudharsan and Jos Buttler open for GT in most fixtures. Sudharsan anchors with the strike rotation through the powerplay; Buttler takes the boundary-hitting risk against the new ball and sets up the platform for the middle overs. Shubman Gill slots in at three and plays the long innings — his average ball count per innings is the highest in the squad because the Ahmedabad surface lets him bat through.

The middle-order is built around David Miller when the franchise wants a left-hander in the middle overs, with Rahul Tewatia as the spin-bowling allrounder finisher. The franchise's batting depth is the deepest in the league — six batters in the top seven can score at a strike rate above 140 on a flat deck. The captain matrix on GT rewards the role-locked anchors and the powerplay aggressors in equal measure.

Bowling

Pace and spin

The GT pace battery runs through Mohammed Shami as the powerplay and death-overs specialist, with the seam allrounders rotating fixture to fixture. The franchise prefers pace on the flat Ahmedabad deck; the surface does not reward spin unless the ball grips in the second innings on a used square. Rashid Khan is the lone spinner who takes wickets on every surface and is the captain's preferred middle-overs match-up against right-handers.

The pace-spin balance on GT is roughly 65-35 in favour of pace on flat decks. When the franchise plays an away fixture at Chepauk or Kolkata, the balance shifts to 50-50 because the surface starts to grip from over six. The differential captain on a slow away deck is Rashid Khan when his role share expands to four overs at the death.

Allrounders

The GT allrounder pair

Rashid Khan and Rahul Tewatia form the GT allrounder axis. Rashid bats in the middle order and bowls his four overs in the middle phase; Tewatia is the finisher at seven or eight with a left-arm spin option on the side. The pair's role share is the most consistent in the squad, and the captain matrix on slow away decks collapses to one of them as the safer captain read.

On flat decks, Rashid is the captain because his wicket-taking ceiling is unmatched; Tewatia is the captain on slow decks where his left-arm spin matches up against a right-heavy opposition. The pair's combined bat-and-bowl output is what the desk tracks when assessing whether the GT captain pool compresses or widens on a given fixture.

Bench

Impact-player slot and rotation

The GT impact-player slot has rotated between a third seamer on flat decks and an extra batter on slow decks. The franchise prefers the third seamer when the opposition reads as right-hand dominant and the death overs need reinforcement; the extra batter is the read when the franchise is batting first and wants a sixth-batter option in the middle.

Watch for the impact-player announcement at the toss — that is when the differential captain reads become clearest on a GT fixture. The franchise does telegraph the rotation in the warm-up coverage; the desk logs the telegraphed slot and adjusts the captain matrix within minutes.

Frequently asked

Questions our readers ask

The Narendra Modi Stadium surface plays flat and the square boundaries are short, so the GT top-order batters get value runs through the powerplay and the middle overs without the bowlers holding them back.

Rashid remains a Tier-1 captain candidate on every fixture where he is taking wickets, but with Shubman Gill leading the batting, Gill is the captain on flat decks and Rashid is the captain on slow away decks.

Sai Sudharsan as the anchor, Jos Buttler as the powerplay aggressor, and the death-overs seamer who rotates fixture to fixture.

Venue read

How Gujarat Titans read at the Narendra Modi Stadium

Ahmedabad's flat-deck identity

The Narendra Modi Stadium is the flattest deck in the league. The ball comes onto the bat through the powerplay; the spinners don't grip until the 12th over on a fresh surface; the square boundaries invite the pull and the cut. Totals above 200 are the norm and the franchise reads as a bat-first side when winning the toss on a fresh square. The captain matrix on GT rewards the batters who take the boundary-hitting risk early.

On a used Ahmedabad square, the surface starts to slow down and the spinners come into the game from over eight. The captain matrix on a used Ahmedabad square collapses to Gill and Rashid as the only Tier-1 captain candidates. The desk tracks the square's match history from the IPL portal and updates the matrix within the first three overs of the innings.

The away-venue tax for GT

GT's away fixture tax is the lowest in the league on flat decks (Bengaluru, Hyderabad, Mumbai) and the highest on slow decks (Chennai, Kolkata). The franchise builds its home XI around a flat-deck profile — top-heavy batting, third-seam option — and that profile translates cleanly to most away venues except the slow turners. On a Chepauk away fixture the franchise is forced to play an extra spinner, which compresses the batting depth.

The captain matrix widens on slow away fixtures because the differential pool expands. The Gill-or-Rashid captain question is settled by the venue; the Buttler-in-the-top-three question is settled by the opposition's new-ball pair; the impact-player seam option is settled by the surface. Tracking how Rashid uses his bowling overs on away fixtures is the single most useful away-venue read on GT.

Travel and the back-to-back blocks

GT's travel pattern in 2026 is moderate — the franchise plays home-and-away blocks of two to three matches with longer turnarounds than most. The captain matrix on a back-to-back fixture reads differently from the matrix on a rested fixture. Watch for the workload announcements around Mohammed Shami: when Shami is rested, the franchise rotates in the third-seamer profile and the captain pool widens by exactly one name.

On a five-day turnaround after an away block, the franchise typically rests one of the seam allrounders and brings in the batting backup. The captain matrix on those fixtures treats the rested player as a Tier-3 read at best. The desk logs the workload announcements within an hour of the press conference and updates the matrix before the squad confirmation.

Pitch history and dew at Ahmedabad

Ahmedabad's dew history is the second-most useful public input on a GT home fixture, behind the toss call. When the evening humidity sits above 60 per cent at the toss, the second-innings chase becomes materially easier; the ball comes onto the bat, the spinners lose their grip, and totals in the 180s become gettable. The dew forecast drives the captain matrix more than the surface reading — Gill's bowl-first preference flips on dew nights because the chase advantage is too large to ignore.

The Ahmedabad pitch history over the last three seasons shows a clear flat-deck bias. The dew reads as a Tier-2 input; the surface reads as a Tier-1 input because the deck rarely changes match to match. The desk logs both before the toss and updates the captain matrix within minutes.

Captain-shortlist pattern

The three-name shortlist on a typical Ahmedabad fixture

Safer captain — Shubman Gill on a flat deck

Shubman Gill is the safer captain on a flat Ahmedabad deck. His role share is stable — he bats at three, anchors through the powerplay and the middle overs, and finishes the innings with the lower order on a chase. On a flat deck with the dew in the second innings, Gill's anchor role compresses to a finish role and his ceiling climbs. The safer captain is Gill on every home fixture and on every flat-deck away fixture where the chase total sits in the 180-plus range.

The captain read on Gill tightens when the franchise wins the toss and bowls first; it loosens when the franchise bats first and the surface reads slow. The desk treats Gill as Tier-1 captain candidate on the chase and Tier-2 when GT bats first on a slow away deck.

Balanced captain — Rashid Khan on a slow away deck

Rashid Khan is the balanced captain on a slow away deck. He bats in the middle order, bowls his four overs in the middle phase, and fields at the key catching positions. The role share is locked — the captain doesn't rest Rashid unless there is a workload issue. On a slow deck, Rashid's bat-and-bowl output compresses the captain pool because nobody else in the franchise carries the same combined role share.

The balanced captain on Rashid tightens on the away fixture where the surface reads dry; it loosens on flat home fixtures where the bowling role compresses and the batting role becomes the dominant captain lever. The desk's read on Rashid is that he is the safest Tier-1 captain when the franchise is bowling first on a used away square.

Differential captain — Jos Buttler on a flat chase

Jos Buttler is the differential captain on a flat Ahmedabad chase. His ownership sits mid-range because most fantasy readers default to the anchor-captain on a home fixture; when the deck is flat and the chase total is high, Buttler's ceiling climbs above the anchors. The differential comes from the read on the surface — if the deck is true and the chase total sits above 180, Buttler is the captain.

The differential read on Buttler tightens when the opposition carries a quality wrist-spinner who can match his aggression; it loosens when the opposition's spin attack is right-arm orthodox and Buttler can take the risks early. The desk tracks the opposition's spin profile before locking Buttler as the differential captain.

When the GT captain pool compresses

The captain pool compresses on the days when Gill is confirmed in the XI and the surface reads flat. On those days the safer captain is Gill, the balanced captain is Rashid, and the differential captain is Buttler — the captain pool narrows to three names and the differential plays weaken. Watch for those days because the grand-league captain contest becomes a coin flip between Gill and Buttler.

The pool widens on slow away fixtures where Rashid's bowling role expands and the franchise needs a wicket-taker in the captain slot. On those days the seam allrounders enter the captain conversation. The desk logs the surface reading within three overs of the innings and adjusts the captain matrix accordingly.

Post-match audit pattern

How the desk audits every GT fixture

1

Pre-toss frame vs the actual Ahmedabad surface

The desk compares the pre-toss Ahmedabad surface call against what actually played. The comparison covers the toss, the confirmed XI, the captain matrix call, the role share on Gill and Rashid, and the dew reading at the toss. The audit names what the desk got right and what the desk missed in plain language on the page.

2

Captain matrix delta on Gill and Rashid

The captain matrix delta is logged for every GT fixture. The delta is the difference between the desk's recommended captain (typically Gill on a flat deck, Rashid on a slow deck) and the captain who actually scored highest at that role. The audit stores the delta and feeds the desk confidence score that aggregates across the season.

3

Role share check on the spin unit

The role share check compares the desk's projected Rashid role share against the actual overs he bowled and the wickets he took. The check is the single most useful audit on GT because the spinner's role share is what the desk most often gets wrong — and what most fantasy readers want verified on an Ahmedabad fixture.

4

Edit for the next Ahmedabad fixture

The desk publishes one edit per GT fixture for the next match. The edit is short and dated; it covers the surface read, the role share change, the workload note, and the impact-player rotation. Tracking the edits over the season is how the desk's GT framework compounds into a usable prediction by the business end of the tournament.

FAQ recap

What readers ask about the GT franchise desk

Why does the GT desk need a separate page from the league desk?

Because Ahmedabad's flat-deck behaviour doesn't show up in a league-level read. The captain matrix on an Ahmedabad fixture is the opposite of the captain matrix on a slow away fixture, and a league-level page averages that away. The GT page exists to keep the surface-specific read sharp and the differential captain pool narrow.

Where does the GT desk sit in the prediction stack?

The GT desk sits between the league-level reads (predictions, fantasy-tips) and the player-level reads (player pages for Gill, Sudharsan, Buttler, Rashid, Shami). The franchise page is the place to land when you want the captain matrix for a GT home or away fixture in the next 48 hours.

How often does the GT page update?

The GT page updates weekly and within hours of any confirmed squad or captaincy announcement. After every GT match, the squad section, the captain matrix, the Ahmedabad venue read and the differential pool are refreshed for the next fixture.

Is the GT page editorial-only?

Yes. The GT page does not accept deposits, does not run contests, does not promote a specific fantasy platform. The coverage is editorial — anchored to public sources, corrected when wrong, audited every match against the actual Ahmedabad surface and the actual role share.

Reading the franchise

Where the GT squad reads sit this week

Top-order reads — Gill anchor, Buttler aggressor

The GT top-order this week sits in a commanding position. Sudharsan opens and anchors; Buttler opens and takes the new-ball risk against the seam attack. Gill holds the number-three slot and plays the long innings. The captain matrix on the top three is stable on a flat deck and slightly compressed on a slow away deck where the middle overs come into the game earlier than usual.

Middle-order depth — Miller and Tewatia as finishers

The GT middle-order depth is the franchise's headline strength. Miller, Tewatia and the impact-player slot cover overs 11 through 18 in most fixtures; the franchise rarely loses wickets in clusters in the middle overs because the role share is locked. The differential reads on the middle order come from the impact-player slot when it favours a finishing option.

Allrounder pair — Rashid Khan locks the captain matrix

Rashid Khan is the franchise's most reliable role-share player and the wicket-taking anchor. Tewatia is the spin-bowling finisher at seven or eight. The pair's combined bat-and-bowl output is what the desk tracks when assessing whether GT's captain pool compresses or widens on a given fixture. On slow decks the pair compresses the pool; on flat decks it widens.

Bowling intent — Shami at the death, Rashid in the middle

The GT bowling intent this week reads consistent. Rashid Khan takes the middle overs; the pace battery of Shami and the rotating seamers holds the powerplay and the death. The captain matrix on the bowlers depends on which phase is highest-value; the differential reads come from the bowler held back for the second innings on a slow away deck.

Play now