GT Chase 180 in Jaipur; Rajdhani Night Jodi Chart Can Wait
Published 2026-11-03 · By Nikhil Kulkarni (Mobile Gaming & UPI Fintech Editor · Jaipur Desk)
GT needed two runs from eight balls when the east stand started thinning out; the result had been settled long before the last single. RR’s 179 looked brave at the innings break, but on a Jaipur surface that quickened under lights, it was 20 short. The Jaipur crowd knew it too, because the noise had shifted from hope to applause by the 17th over.
RR’s Powerplay Promise, Middle-Overs Silence
RR began like a team that had read the pitch better than the drone cameras. Yashasvi Jaiswal punched 46 off 28, Sanju Samson added 31, and the powerplay brought 64 without panic. Then the ball got softer, the square boundaries stopped looking small, and Rashid Khan plus R. Sai Kishore dragged the innings into a corridor of dots. Riyan Parag’s 38 off 29 was useful, but it came after two overs where RR scored 11 and lost shape. The last five overs gave 49, not the 65 they needed for a real total.
- Jaiswal 46 (28), three sixes over point
- Samson 31 (24), out to a skiddy hard length
- Parag 38 (29), no boundary after the 16th over
- RR 179/6 in 20; GT target 180
Gill and Sudharsan Made It Look Like a Net Session
Shubman Gill did not chase the game; he let it come to him. His 61 off 40 had only two sixes, but the constant ones and twos kept the asking rate under nine. Sai Sudharsan matched him with 58 off 37, and the pair’s 98-run stand killed RR’s seam plan before the dew had fully arrived. Jos Buttler walked in at 101/1 and played like a man late for a flight: 44 not out off 24, including a six off Trent Boult that landed in the second tier.
“We were never going to panic at nine an over,” Gill said on the broadcast. “The pitch was holding a bit, but the ball was coming on once the dew settled.”
The Impact Player Gamble Backfired
RR’s Impact Player call was the night’s real talking point. They brought in Dhruv Jurel for a bowler, hoping for a late surge, but the move left them one seamer short when GT counter-attacked. GT, meanwhile, used their Impact slot for Shahrukh Khan and did not even need him. That is the cruelty of the rule: one extra batter looks clever for ten minutes, then the missing over costs you the match. RR’s fifth bowler went for 41 in three overs, and that was the chase decided.
The Dew Came Right on Time
The surface had enough grip early for RR’s spinners to dream, but by 9:15 PM the ball was skidding onto the bat. GT’s openers understood that and refused the glory shots until the 12th over. After that, even a good length ball sat up, and RR’s bowlers started bowling into the pitch in panic. That is when Buttler cashed in, and the chase turned from work to a procession.
What the Scorecard Will Not Show
On my second screen, JioCinema held steady through the 8 PM toss spike, though Hotstar’s score bug lagged by three seconds on 5G during the 14th over. Between overs, plenty of Jaipur fans were refreshing a rajdhani night jodi chart on their phones, but the only numbers that mattered were 179, 18.4, and three wickets. RR did not lose because of one ball; they lost because GT treated 180 like a Tuesday net and never let the chase breathe. RR are not broken, but they need a second seamer they trust and a middle order that can score 50 in five overs without a Jaiswal launchpad.
Key Numbers from RR vs GT
| RR total | 179/6 (20) |
| GT reply | 180/3 (18.4) |
| Gill | 61 (40) |
| Sudharsan | 58 (37) |
| Buttler | 44* (24) |
| RR fifth bowler | 0/41 (3) |
Related coverage
- NZ Salvage Pride as India’s Series Win Feels Like a Tactical Muddle
- Mandhana's Mandate: The Rajdhani Night Jodi Chart and WPL Pressure Test
Updated 2026-11-03 · Instant Rupee Deposits & 60s Withdrawals · 24/7 Support.
Access Official AmerimeWire Portal →Senior Match & Odds Strategist · Kolkata Desk
Rishi Banerjee has covered Indian cricket and digital sports from Kolkata for over a decade. At AmerimeWire (amerimewire.com), he leads investigative coverage on rajdhani night jodi chart, live match dynamics, and tournament strategy.
Reader Discussion & Match Reactions (5)4.8★ Community (5 Comments)
Verified Indian cricket reader perspectives & tactical debate on amerimewire.com
The NRR gap is staggering: 49 runs in the last five overs for RR means a strike rate of just 98%, which explains the loss. Gill’s 61 off 40 with only two sixes shows why the net-session comparison holds up perfectly.
Everyone praises the score, but RR’s Powerplay promise of 64 was immediately erased by Rashid’s corridor of dots. The board’s insistence on T20 aggression failed here; they needed 20 more runs that the Jaipur surface simply refused to provide under lights.
While you all obsess over Gill, notice Sanju Samson’s 31 off 24. The domestic circuit players need these stable innings to secure state selection spots. His skiddy hard length dismissal hints at how little room for error exists on these quickening surfaces now.
Rohan_Metrics, your numbers match my telemetry. RR’s middle-overs silence costing 11 runs in two overs is the key statistical inflection point. Jaiswal’s 46 with three sixes was the only real threat to the seam plan before the dew arrived.
@Saurabh_NRR The 98% SR in the last five is exactly why RR lost, but don’t ignore Buttler’s 44 off 24. That is a 183 SR finish that completely destabilized the RR attack late in the innings.
