RCB’s Big Qualifier Swing: Rabada’s ₹2.81cr Boost as GT Misstep Costs Big

Rajasthan? No—this one belonged to Bengaluru and a late swing in momentum that turned a competitive start into a runaway playoff statement. Royal Challengers Bengaluru built a solid platform, then a dropped chance in the 14th over flipped the match’s shape, before the bat did the rest in Dharamsala.

Quick facts

  • RCB reached 254/5, the highest team total ever in an IPL playoff.
  • Rajat Patidar finished unbeaten on 93 off 33 (nine sixes, five fours), the fastest IPL innings of 90+ runs.
  • GT were bowled out for 162, losing by 92 runs.
  • The turning point came in the 14th over when a leading edge off Patidar was missed at deep third, and a later chance at deep square leg was also dropped.
  • Qualifier 1 took place at Dharamsala on May 26, 2026 (RCB vs GT).

After being put into bat, RCB began with real intent. Virat Kohli and Devdutt Padikkal carried the opening phase to 76/1 in the powerplay, forcing Gujarat Titans to find a better rhythm.

GT responded with pressure that tightened the scoring rate. Rashid Khan delivered in disciplined spells, while Jason Holder made the breakthrough impact felt immediately—striking twice in three balls to remove Kohli for 43 and Padikkal for 30. Kulwant Khejroliya also helped keep things under control as RCB slipped into 134/3, with the innings not quite collapsing but certainly stalled.

Rajat Patidar arrived at the crease looking to shift the gears. Prasidh Krishna came on for the 14th over, and that segment would define the rest of the chase.

The 14th over that changed everything

First, a leading edge from Patidar fell between the wicketkeeper and deep third, resulting in a clean reprieve as no one held the chance. Then, Patidar struck again—pulling Krishna straight to Kagiso Rabada at deep square leg.

Rabada couldn’t hold it. The missed chance didn’t just delay the wicket; it allowed Patidar to stay in and keep finding momentum when GT needed an exit to reset the chase.

By then, RCB were 135/3, with Patidar already on 16 off 12. The next over brought a further blow to GT’s discipline: Khejroliya leaked 28 runs, with the damage coming through a mix of misfields, two no-balls, and a wide. Suddenly, the game’s tempo belonged to RCB.

From there, the innings opened up fully. Patidar and Krunal Pandya added 95 together, with Krunal contributing 43 before Rabada finally broke the partnership. Even that wicket couldn’t change the end result—RCB were already in the upper atmosphere.

Patidar closed the innings unbeaten on 93 from 33 deliveries, smashing nine sixes and five fours. His 90-plus score at that pace became the fastest such innings in IPL history. RCB then accelerated brutally at the end as they smashed 114 runs in the final six overs to finish on 254/5—also the highest total ever by a side in an IPL playoff.

GT’s chase never properly took hold, turning into something closer to a formality than a contest. Sai Sudharsan was dismissed when his bat slipped onto the stumps for 14. Shubman Gill was removed by Bhuvneshwar Kumar for 2, and Jos Buttler departed for 29.

Nishant Sindhu and Jason Holder also fell in the same Rasikh Salam over. With the score at 51/5, the match effectively tilted away from GT, leaving only Rahul Tewatia’s 68 off 43 as a last attempt at resistance.

Eventually, Gujarat Titans were all out for 162, and RCB won by 92 runs.

The price of one fumble

The impact of that deep square leg drop was measured through a win-probability framework that scores every delivery in a match. On the missed catch itself, Rabada’s failure to complete the chance was assigned a direct fielding penalty of 8.47 impact points—an immediate cost tied to the situation and Patidar’s threat level at that moment.

At a conversion rate of ₹0.02 crore per impact point, that single lapse translated into ₹16.94 lakh in instant value lost for GT. That number is the smaller part of the story.

The bigger cost came from what followed because the catch wasn’t taken. Every ball Patidar played after the reprieve carried its own impact score, and the cumulative damage from those deliveries added up to 131.88 impact points of batting benefit. In monetary terms within the same model framework, that cascading batting advantage equals ₹263.77 lakh.

Put together, the direct penalty from the dropped chance and the subsequent run of damage cost Gujarat Titans ₹2.81 crore in total match impact.

Rabada’s per-game share of his ₹10.75 crore season contract was ₹67.19 lakh, while the drop-related cost exceeded that figure by more than four times in the same impact-to-money conversion.

The scenario also mattered in cricket terms: had Rabada held on, Patidar would have walked off at 21, the partnership with Krunal would likely never have ignited, and 254 would have become far more chaseable under different pressure dynamics. Instead, a pull shot finding the fielder became the turning point of Qualifier 1, and Rabada’s missed chance didn’t just drop a catch—it dropped GT out of the match.

Methodology note

Impact values come from the WPA Impact Index, a ball-by-ball framework that scores each delivery across batting, bowling, and fielding by estimating win probability swing in the match context, designed by the author. The monetary conversion of ₹0.02 crore per impact point is calculated using GT’s match-specific cost deployment. The “post-drop damage” figure represents the cumulative batting impact generated by Patidar from the delivery immediately after the missed catch until the end of his innings.

All figures are model outputs built from IPL 2026 Qualifier 1 data for RCB vs GT at Dharamsala on May 26, 2026. The WPA Impact Index is independent and unaffiliated with the BCCI, the IPL, or either franchise. Monetary values are modelled equivalents, not actual financial transactions.