Delhi Capitals chase 226, win seven
- Delhi Capitals chased 226 in Jaipur and beat Rajasthan Royals by 7 wickets, finishing on 226/3 in 19.1 overs after a 451-run shootout. (iplt20.com) - KL Rahul made 75 off 40 and Pathum Nissanka 62 off 33, putting on 110 up top after Riyan Parag’s 90 had lifted RR. (espncricinfo.com) - It was Delhi’s highest successful IPL chase and snapped a three-match slide, pushing them back upward in the table. (iplt20.com)
This was an IPL batting game in its purest form — flat pitch, short bursts of chaos, and a target that should have felt safe but didn’t. Rajasthan(iplt20.com)the whole thing look less dramatic than a 226 chase is supposed to look. That matters because Delhi had lost three straight before this, and because a chase this big can reset how a team feels about its season. (iplt20.com) ### How big was the chase? Huge. Delhi’s 226/3 was their highest successful cha(iplt20.com)than IPL meeting. Targets above 220 are usually built to survive one or two good partnerships. Delhi blew through that logic by getting one massive opening stand and then never really letting the required rate squeeze them. (espncricinfo.com) ### What did Rajasthan do right? Riyan Parag gave them the innings that should win you (iplt20.com)om Donovan Ferreira, who smashed 47 not out off 14. The odd part is that Rajasthan were 12/2 inside two overs after losing Yashasvi Jaiswal and Vaibhav Sooryavanshi. From there, 225/6 was a rescue act and a launch sequence rolled into one. (espncricinfo.com) ### So why w(espncricinfo.com)t quickly enough that the equation never turned ugly. Nissanka’s 62 off 33 gave the innings its early punch. Rahul’s 75 off 40 gave it control. That pairing is basically the whole story — one batter forcing the pace, the other making sure the chase stayed on rails. (espncricinfo.com) ### Wh(espncricinfo.com) 225 had already shrunk from “mountain” to “very expensive sprint.” Once the openers crossed 100 in the ninth over, the chase stopped being about survival and became about clean finishing. Rajasthan needed wickets in a cluster. They never got them. (rajasthanroyals.com) ### Did Delhi need more than the openers? Yes(espncricinfo.com)hat is the luxury a 110-run opening stand buys you. It turns the middle overs from a risk zone into a handoff. Delhi lost only three wickets all chase, which tells you Rajasthan never found sustained control with the ball. (timesnownews.com)k 3/40 and removed Jaiswal early, then came back for Parag and Ravindra Jadeja at the death. On a surface where almost everyone was getting hit, “good enough” mattered. If Rajasthan had found another 15 or 20 runs, this becomes a different conversation. (espncricinfo.com) ### Why does this (timesnownews.com)Delhi that can chase at the very top end of IPL scoring — not through one freak over, but through sustained batting depth and tempo. That is a much scarier signal to the rest of the league. (economictimes.indiatimes.com)ka turned the chase into a statement — and maybe into the point where Delhi’s season starts moving the other way. (espncricinfo.com)