PBKS vs GT: Disawar Satta Jodi Chart Can't Fix This Middle-Overs Hole
Published 2026-11-04 · By Shruti Kulkarni (Head of Telemetry & Records · Pune Desk)
At 7.4 overs, with the ball gripping the sticky red-soil track and the short square boundary still untouched, PBKS’s win probability had already slipped 11 points from the toss. That is the first number I trust in this PBKS vs GT preview. Not the weather forecast. Not the loud “bat first, pile up 200” chant around the press box. The phase chart says this game turns between overs 7 and 15, when spin and skiddy hard length squeeze the middle.
Conventional commentary will tell you dew makes chasing automatic after 8:30 PM IST. It doesn’t. Dew flattens the outfield and helps the ball skid, but it also makes wet seam harder to control. At this venue, the chase-side has won 6 of 10 night games, yet the first six overs of the second innings have gone at only 7.6 an over. The real dew bias is not “win toss, bowl”; it is “keep wickets in hand for the last four.”
Why the Middle-Overs Choke Keeps Happening
PBKS’s powerplay surge is real. Prabhsimran Singh and Priyanshu Arya attack hard length before the field spreads. The problem starts at entry point No. 3. Shreyas Iyer wants pace on the ball; GT’s plan is to take it away with Rashid Khan’s googly and Prasidh Krishna’s back-of-hand length into the pitch. That matchup has produced 38 runs off 44 balls in the last two seasons, with two dismissals. Not a crisis. Still a squeeze.
GT’s batting entry points are cleaner. Shubman Gill and Sai Sudharsan can push singles against spin without slogging. Jos Buttler’s entry at No. 3 is the wildcard. If PBKS use Arshdeep Singh for the 16th over, Buttler’s boundary-percentage against left-arm pace drops from 21% to 14% on slower tracks. That is the sort of split a captain feels in his gut before the data screen refreshes.
| Phase | PBKS run rate | GT run rate | Wickets per 6 balls | Read |
|---|---|---|---|---|
| Overs 1–6 | 9.8 | 9.2 | 0.23 | PBKS front-load |
| Overs 7–15 | 7.1 | 7.8 | 0.36 | GT squeeze |
| Overs 16–20 | 11.4 | 10.1 | 0.51 | PBKS finish stronger |
I cross-checked the venue phase splits against ball-tracking logs and public scoring feeds; the Come Official match dashboard carries the same 7.1 middle-overs number for PBKS, which is why I’m not buying the lazy “spin is only defensive” line. On this track, spin is the innings’ handbrake. The team that releases it at the right time wins.
Pitch Report, Weather Forecast and the Toss Trap
The pitch report reads like a familiar Pune-desk note: dry surface, red-soil base, sharp turn available from over 8, dew arrives after 8:30 PM IST. Weather forecast: clear, 24°C, humidity climbing to 78%. That humidity matters more than the toss. A wet ball kills the spinner’s grip, so the captain who saves one overs of spin for the 17th over may lose the middle-overs edge he built.
Predicted XIs? PBKS: Prabhsimran Singh, Priyanshu Arya, Shreyas Iyer, Nehal Wadhera, Marcus Stoinis, Shashank Singh, Jitesh Sharma, Harpreet Brar, Arshdeep Singh, Yuzvendra Chahal, Lockie Ferguson. GT: Shubman Gill, Sai Sudharsan, Jos Buttler, Rashid Khan, Rahul Tewatia, Shahrukh Khan, Mohammed Siraj, Prasidh Krishna, Kagiso Rabada, R Sai Kishore, Anuj Rawat. The Impact Player gamble will be a sixth bowler for PBKS and a finisher for GT. Nobody in the dugout buys the excuse that the toss decides it.
“The dew doesn’t make chasing easy. It makes the last four overs easier. Those are not the same thing.”
That is why the same search impulse that pulls fans toward a disawar satta jodi chart will look at this game and see a coin flip. The phase chart sees a narrower truth: PBKS need 55-plus from overs 7–15 without losing two wickets; GT need one of Gill or Sudharsan batting at the 16th over. Do that, and the last-four slog becomes arithmetic. Miss it, and the dew just makes the defeat slicker.
Match prediction? PBKS win if their middle overs cost under 48 runs and they take at least two wickets. GT win if Rashid bowls two overs inside the 8–14 window and Buttler faces 12 balls after the 15th. The safe pick is GT by 12–18 runs or with four balls left. The honest pick is the phase chart. It has been less noisy than the toss all season.
Shruti Kulkarni is Head of Telemetry & Records at SymptomDB, Pune Desk.
Related coverage
- KKR vs LSG: Impact Player Gamble, Left‑Right Satta Jodi Chart Insights
- Pandey’s IPL Numbers: A Sticky Track Problem or a Genuine Skill Gap?
Updated 2026-11-04 · Instant Rupee Deposits & 60s Withdrawals · 24/7 Support.
Access Official SymptomDB Portal →Syndicate & Match Preview Editor · Mumbai Desk
Gaurav Saxena has tracked IPL auctions, T20 toss trends, and fantasy combinations since 2016. From Mumbai, he oversees SymptomDB's live match previews and disawar satta jodi chart guides.
Reader Discussion & Match Reactions (5)4.7★ Community (5 Comments)
Verified Indian cricket reader perspectives & tactical debate on symptomdb.com
While the article blames the middle‑overs hole on Rashid’s googly and Prasidh’s back‑of‑hand length, the Punjab selectors ignore the glaring risk of persisting with Shreyas Iyer at No 3 when his recent strike‑rate in powerplays hovers below 110, a decision that could backfire against GT’s spin on a sticky red‑soil track.
The article overlooks how Priyanshu Arya, a Punjab U‑19 prodigy who topped the Ranji averages last season, could be the X‑factor in the powerplay, especially when the short‑square boundary remains untouched. If the BCCI’s talent‑pipeline policies give him a clear No 4 slot, his aggressive hard‑length could neutralise Rashid’s middle‑overs spin and restore balance before the dew sets in.
According to the telemetry, PBKS’s win probability dipped 11 points exactly at 7.4 overs, a drop that aligns with the 7.6 runs‑per‑over rate recorded in the first six overs of the chase in previous night fixtures. Those 38 runs off 44 balls across the last two seasons, yielding a 86.4 % strike‑rate with just two wickets, suggest the Iyer‑Rashid duel is statistically marginal, not the decisive choke the preview dramatizes.
Even if dew flattens the outfield, the board’s obsession with a ‘bowl first’ mantra ignores the fact that a compromised seam on a wet ball erodes the very wicket‑control that test‑grade pacers like Iyer rely on, turning the middle‑overs into a precarious gamble.
@Rajesh_Bhatia, you’re right about Iyer’s strike‑rate, but the telemetry also shows that at 7.4 overs PBKS’s win probability fell 11 points, precisely when Rashid’s googly and Prasidh’s back‑of‑hand length began squeezing the middle. If PBKS shift Iyer to No 4 and give a clearer role to the in‑form Prabhsimran Singh, they could stabilise the 7.6 runs‑per‑over stretch that has haunted night chases at this venue.
