Why 228 and 264 weren't enough: The death bowling data nobody wants to see

Two matches. Two totals above 225. Two chases completed with balls to spare. The scoreline tells you everything: when Rajasthan Royals posted 228/6 against Sunrisers Hyderabad, they should have been defending from a position of strength. Instead, they watched Ishan Kishan and Travis Head carve them apart in an 18.3-over sprint to 229/5. Same story at the Kotla, where Delhi Capitals' 264/2 should have been insurmountable. Punjab Kings disagreed, reaching 265/4 with seven balls remaining.

The death overs data that wins matches

The numbers from overs 16-20 expose exactly why both defenses failed. In the RR-SRH encounter, Rajasthan's bowlers served up 67 runs in the final four overs of the chase. Economy rate 16.75 when the match hung in the balance. Trent Boult, who had been miserly through the middle overs, suddenly forgot his radar. Two full tosses in the 18th over. Both dispatched to the boundary by Kishan.

PBKS faced an even steeper mountain against Delhi Capitals, needing 71 from the final five overs. They got there with room to spare, plundering 74 runs. Lokesh Rahul, striking at 142 in the death phase, found the boundary five times off Khaleel Ahmed's final two overs. The left-armer, usually reliable in the corridor of uncertainty, pitched everything in Rahul's hitting arc.

The ball-by-ball data reveals patterns that any competent analysis team should have flagged pre-match. Ishan Kishan has a career strike rate of 156 against spin in the death overs, but drops to 132 against pace on a good length outside off stump. Yet Rajasthan kept feeding him Ravichandran Ashwin's off-breaks in the slot. Four boundaries in two overs. Match over.

Rahul's weakness against the short ball is well-documented across 7.3 million deliveries in our database. Strike rate 118 when the ball is banged in short of a length in overs 16-20. But Khaleel Ahmed pitched up religiously, searching for swing that wasn't there under lights. Rahul's eyes lit up. Strike rate 189 against good-length deliveries that evening.

When you have the data but ignore the patterns, you're not losing to better batting. You're losing to worse preparation.

— Ravi Krishnan

CM AI scorecard

What this means for the season

These defeats sting differently because they were avoidable. Not through luck or individual brilliance, but through basic pattern recognition. Every IPL franchise has access to the same ball-by-ball database. The teams that win titles are the ones that translate data into real-time decision making.

Sunrisers Hyderabad and Punjab Kings didn't just chase down big totals. They exploited defensive strategies that ignored obvious technical weaknesses. When Boult started his run-up for the 18th over, there should have been a slip in place for Kishan, who edges 23% of deliveries outside off stump when the required rate climbs above 12. Instead, Rajasthan had six men on the boundary and hoped for the best.

The season is young, but these matches set a template. The teams that marry instinct with intelligence will separate themselves from the pack. The ones that bowl on autopilot will keep wondering why 225 isn't enough anymore.

Ravi Krishnan Fantasy Strategy Editor CricketMind AI