Delhi chase 226, beat Rajasthan by 7

Delhi Capitals just pulled off the kind of chase that can reset a season. They ran down 226 against Rajasthan Royals in Jaipur, won by 7 wickets with five balls left, and finally snapped a three-match losing streak. That matters because Delhi had started to look like a side drifting out of the playoff picture. Instead, they produced their highest successful chase in IPL history — and did it in a game that never really slowed down. (iplt20.com) ### How big was this chase? Huge. Rajasthan made 225 for 6, Delhi replied with 226 for 3 in 19.1 overs, and the match aggregate hit 451 runs. That made it the highest-scoring IPL game involving these two teams, but the more important part is simpler — 226 is not a total you usually hunt down cleanly with only three wickets lost. Delhi didn’t just survive the chase. They controlled it for long stretches. (espncricinfo.com) ### What gave Rajasthan that total? Riyan Parag did the heavy lifting. He made 90 from 50 balls and rebuilt the innings after Rajasthan slipped to 36 for 2 inside five overs. Dhruv Jurel added 42, then Donovan Ferreira detonated at the end with 47 not out from 14 bal(espncricinfo.com)aiswal and later came back to dismiss Parag and Ravindra Jadeja. (espncricinfo.com) ### So why didn’t 225 hold up? Because Jaipur turned into a chase ground again. The ball did a bit early — enough for Rajasthan to wobble and enough for Delhi to think they had a chance — but once the surface settled, the bowlers had very little margin. ESPNcricinfo’s matc(espncricinfo.com)at this venue. If you didn’t nail yorkers and pace changes, hitters could line you up. (espncricinfo.com) ### Who broke the chase open? KL Rahul and Pathum Nissanka. Nissanka made 62 from 33 and gave Delhi the kind of fast start that keeps a 226 chase from becoming arithmetic panic. Rahul then played the stabilizer and accelerator at once — 75 from 40, enough control to keep w(espncricinfo.com)r than frantic. (espncricinfo.com) ### Where did the game really swing? At the contrast between recovery and closure. Rajasthan recovered brilliantly from 36 for 2, but Delhi closed better. Starc’s 3 for 40 stopped the innings from becoming 240-plus, which sounds small until you remember the margin be(espncricinfo.com) one side kept finding momentum; the other never found the kill shot. (espncricinfo.com) ### What does this mean for Delhi now? It keeps them alive, but more than that, it changes the mood. Losing three straight can make every chase feel heavier and every bowling spell look shorter than it is. A win like this does the opposite. Delhi now have proof that (espncricinfo.com) clarity start blending together. (msn.com) ### And what’s the problem for Rajasthan? Rajasthan’s campaign keeps slipping into the same trap — enough batting to scare teams, not enough control to finish them. A total of 225 should force mistakes. Instead, Delhi got rhythm. That leaves Rajasthan with the annoying kind of question every contender hates: is the attack actually good enough on flat nights, or are the batters being asked to win games twice? (espncricinfo.com) ### Bottom line? Delhi didn’t just win a shootout. They showed they can survive one of the hardest assignments in T20 cricket — a 226 chase on the road — and that keeps their season breathing. Rajasthan, meanwhile, got the uglier lesson: on these surfaces, “enough runs” may not be enough at all. (iplt20.com)