‘I can’t fathom it’: Ashwin left ‘baffled’ by David Miller’s decision in DC’s one-run defeat | Cricket News – The Times of India


‘I can’t fathom it’: Ashwin left ‘baffled’ by David Miller’s decision in DC’s one-run defeat | Cricket News – The Times of India
David Miller and Kuldeep Yadav

While much of the cricket fraternity expressed sympathy for David Miller after Delhi Capitals’ heartbreaking one-run defeat, former India spinner Ravichandran Ashwin stands baffled and stunned by the decision of the South African batter in the final moments of the chase.Delhi appeared to be in control towards the end, with Miller striking crucial boundaries and bringing the equation down rapidly. However, the match turned in the final over bowled by Prasidh Krishna. On the second-last ball, Miller chose not to take a single, opting to retain the strike,a decision that ultimately increased the pressure.

Watch

Pathum Nissanka reveals KL Rahul’s advice, opens up on powerplay plan

With two runs needed off the final delivery, Miller failed to connect with a slower ball and attempted a desperate run. Jos Buttler’s sharp work resulted in a run-out at the striker’s end, leaving Kuldeep Yadav short and sealing a dramatic one-run victory for Gujarat Titans.Ravichandran Ashwin opened in a video of his Youtube channel, “I am thinking what could have happened to Kuldeep and David Miller. If I was Kuldeep, I would have pushed him to the other end. I can’t understand. I can’t fathom it. It is just beyond me. It is bonkers,” Ashwin said. “Because if you want 4 runs or 6 runs, it was right. You need 2 runs. And what are the odds? You can take 1 run. Kuldeep will at least get into the bat. Or if he doesn’t, you can run away. Even if Kuldeep gets bowled, in a 210 game, if you reach the Super Over, you have done well. I am not able to wrap my head around it,” Ashwin further said.While Ashwin admitted that anyone can make a mistake, he is unable to find logic in the idea behind Miller’s decision to turn down the opportunity of a score-levelling single.“Mistakes can happen with anyone. Everybody can make a mistake. No doubt about it. I am sure David Miller is feeling absolutely gutted at this point of time. But I am not able to wrap my head around the thinking. What was the thinking? I don’t know, man. Delhi has such a strong team. We talked about it. But still, I told you that Delhi might find a way to kick themselves out of the tournament. If you lose like this, you are doing two things,” Ashwin said.Former Delhi Capitals player Ashwin feels Miller’s call hurt his team’s confidence while giving Gujarat Titans a significant psychological edge moving forward.“One, you have shaken the confidence of your team. And second, if a team like Gujarat Titans lost today, they will come back from the tournament thinking how they will reach from here. They will think. there will be a catch-22. But you let them come back from the tournament. But you gave them a lifeline while you’re still stuck at 4 points,” he concluded.


DC vs GT: What was David Miller thinking — why didn’t he run? | Cricket News – The Times of India


DC vs GT: What was David Miller thinking — why didn’t he run? | Cricket News – The Times of India
Delhi Capitals’ David Miller and Kuldeep Yadav after losing by one run vs Gujarat Titans. (Pic credit: IPL)

NEW DELHI: ‘What was he thinking?’. ‘What was he doing?’. ‘Why didn’t he run?’ These were some of the questions that did the rounds in the aftermath of Delhi Capitals’ one-run loss against Gujarat Titans in the ongoing IPL 2026.The ‘he’ in question is David Miller. The South African batter had a whirlwind experience at the Arun Jaitley Stadium on Wednesday.Go Beyond The Boundary with our YouTube channel. SUBSCRIBE NOW!First, while fielding, he picked up an injury on his right hand when he made a dive on the practice pitches to stop a Sai Sudharsan cover drive.Having tried to brush that off, he came to bat but the effects of it became far too clear just 10 balls into the 211-run chase. The blow had already been further exacerbated when he dived to make the crease.At that juncture, DC were 130/3 and needed 81 from 42 balls with KL Rahul well set on 69 from 37 balls. When Miller re-appeared, DC had just lost Tristan Stubbs to a run out and the equation on the scoreboard read: 51 needed from 20 balls. Three balls later, Rahul went for a well-outside-off-ball from Mohammed Siraj and the inside edge was lapped easily by keeper Jos Buttler.The onus and weight of responsibility had suddenly shifted towards the tattered and bruised 36-year-old Miller.He added only 6 from 3 balls upon resumption of his innings as the required rate ballooned to 18.00. And that is where the game turned.Miller hit 6, 4 and 6 off Mohammed Siraj, with the pacer conceding 23 runs in the penultimate over to bring the equation closer. It helped further that GT were penalised for a slow over rate, forcing an extra fielder back into the circle.13 needed from 6 became 8 from 3 balls when Miller got his chance in the final over. Next ball, Prasidh Krishna came around the wicket, bowled into the arc and was duly punished with the resultant six landing in the third tier of the stadium. A massive 106 metre hit!Then came the moment which baffled everyone and will be discussed for weeks at end. A pull shot went towards deep square leg and Miller refused a single with DC needing 2 from 2 balls. Had they completed that safe run, Kuldeep Yadav would have been asked to finish things off or at the very least force a Super Over.Instead, as Prasidh bowled a smart last ball under pressure, DC were unable to add to their tally and were instead caught one run short.Finisher without the finishA few days ago, as Punjab Kings chased down 210 runs against Chennai Super Kings at Chepauk, CSK head coach Stephen Fleming claimed there is no room for finishers in T20 anymore.“Look, I don’t think there is a thing called finishers anymore. It’s right from ball one, everyone is going at a rate of knocks. It’s not ‘build up to the 16th over and then go harder’. Everyone’s going hard from ball one. So the run rates of 10, 11, 12 all the way through are what’s expected and you’re not really getting the big peaks towards the end,” he said.The DC chase, albeit unsuccessful, disproved that theory. If Delhi Capitals were scoring at 10.5 runs an over in the powerplay and 8.77 in the middle, they upped the ante to 13.40 in the final five overs. The 16th over went for 16 runs and Siraj’s 19th produced 23 runs – the joint-highest of the night.Back to the question on Miller’s decision to not run and no one had a fitting answer. Gill believed they had a “chance to win.” DC skipper Axar Patel said things could have gone either way. “I think, this type of close game, you can, you know, point out anything. So I think, yes, we played very good cricket. As I said earlier, in a close chase, in a close game, you can point out a lot of things. But I think in the chase, I think we could have played smarter,” said Axar.DC opener Pathum Nissanka didn’t divulge much when he said, “We haven’t discussed it yet, but sometimes it happens in cricket,” in the post match press conference. Rashid Khan, the Player of the Match, was quite pleased that he wasn’t in Miller’s shoes at that moment.What was going through Miller’s head can only be best explained by him. One can only hazard a guess from the outside. But on the inside, DC would rue this golden opportunity lost.


IPL 2026: Jos Buttler scripts history, enters elite T20 club | Cricket News – The Times of India


IPL 2026: Jos Buttler scripts history, enters elite T20 club | Cricket News – The Times of India
Gujarat Titans’ Jos Buttler (ANI Photo/Rahul Singh)

Gujarat Titans’ Jos Buttler reached a landmark in the IPL against Delhi Capitals, hitting his 600th six in T20 cricket. The England star became the fifth batter to reach this milestone, joining Chris Gayle (1,056 sixes), Kieron Pollard (981), Andre Russell (784), and Nicholas Pooran (712). Buttler’s 27-ball 52 featured five sixes and three fours at a strike rate of 192.59. His five sixes in the first six overs now rank as the second-most for a non-opener in an IPL innings, only behind Suresh Raina’s famous 87 off 25 balls, which included six sixes, against PBKS in the 2014 Qualifier 2 at Wankhede. This innings also ended Buttler’s 16-match wait for a T20 fifty, his last coming for Durban Super Giants against Pretoria Capitals in the SA20 earlier this year. He had a disappointing T20 World Cup, scoring just 87 runs in eight innings at an average of 10.87. So far in IPL 2026, Buttler has scored 116 runs in three innings at an average of 38.66 and a strike rate above 156. Across all T20s this year, he has 422 runs in 19 innings at 23.44 with a strike rate of 140.66, including two fifties and a best of 97*. In the match, after losing Sai Sudharsan cheaply for 12, Buttler and Shubman Gill added 60 runs to steady Gujarat Titans. Gill then partnered with Washington Sundar (55 off 32) for a 104-run stand, helping GT reach 210/4 in 20 overs. Glenn Phillips (14*) and Rahul Tewatia (1*) remained unbeaten. For Delhi Capitals, Mukesh Kumar was the pick of the bowlers with 2/55, while Kuldeep Yadav and Lungi Ngidi took a wicket each. Despite KL Rahul’s 92 off 52, DC fell agonisingly short by one run, with David Miller’s 41 off 20 balls keeping the contest alive until the final delivery.


IPL 2026: Gujarat Titans edge thriller by one run as David Miller’s call costs Delhi Capitals dearly | Cricket News – The Times of India


IPL 2026: Gujarat Titans edge thriller by one run as David Miller’s call costs Delhi Capitals dearly | Cricket News – The Times of India

NEW DELHI: Gujarat Titans finally got their first win of IPL 2026 after a dramatic last-over finish against Delhi Capitals. Chasing 211, Delhi fell just one run short despite a strong effort, ending at 209/8. The match turned on a crucial moment when David Miller refused a single late in the final over, a decision that proved costly.

Watch

Yashasvi Jaiswal reveals RR dressing room mood after third straight win

Last-over drama decides the match

Delhi looked in control towards the end, especially with Miller hitting big shots and bringing the equation down quickly. However, the game changed in the final over bowled by Prasidh Krishna. Miller declined a single on the second-last ball, keeping strike but putting pressure on himself.On the final delivery, with two runs needed, he missed a slower ball and attempted a run, but Jos Buttler ran him out at the striker’s end, leaving Kuldeep Yadav short. Delhi finished agonisingly short, handing Gujarat a thrilling one-run win.

How the match unfolded

Earlier, Gujarat Titans posted a strong total of 210/4, thanks to key contributions from Jos Buttler (52), Shubman Gill (70) and Washington Sundar (55). Buttler’s aggressive start, including multiple sixes, set the tone, while Gill and Sundar kept the momentum going.In response, Delhi Capitals got off to a solid start with KL Rahul (92) and Pathum Nissanka (41) building a strong opening partnership. However, Rashid Khan’s three wickets in the middle overs shifted the momentum.Despite Miller’s late heroics, including a big penultimate over, Delhi couldn’t cross the line. The result marked Gujarat’s first win of the season, while Delhi suffered their first defeat after a promising start.


On-field drama! David Miller and Washington Sundar locked in heated exchange – Watch | Cricket News – The Times of India


On-field drama! David Miller and Washington Sundar locked in heated exchange – Watch | Cricket News – The Times of India
David Miller and Washington Sundar (Getty)

India’s T20 World Cup title defence suffered a significant setback after a crushing 76-run defeat to South Africa in a high-stakes Super 8 clash. The night had begun brightly for the hosts, who reduced the Proteas to 20/3 with a sharp new-ball burst. But what followed was a complete shift in momentum, driven by a calculated counter-attack in the middle overs. David Miller turned the tide with a commanding 63 off 35 deliveries, striking seven fours and three sixes. Calm and assured for most of his innings, he rebuilt South Africa’s total alongside Dewald Brevis and Tristan Stubbs, steering the innings towards a competitive 187/7. However, Miller’s composure briefly slipped during a tense on-field exchange with Washington Sundar. The flashpoint came when Stubbs nudged a single to the leg side and Miller set off from the non-striker’s end. Sundar appeared unhappy, believing Miller had left his crease early before the ball was released, and immediately raised the matter with the umpire. Miller responded by confronting Sundar, leading to a heated argument between the two. On-field umpire Chris Gaffaney stepped in to calm proceedings, and South Africa captain Aiden Markram later joined during the drinks interval to defuse the situation. The precise trigger for the disagreement remained unclear, and the tension did not resurface. Miller was dismissed shortly afterwards, briefly offering India hope. That hope faded quickly. Stubbs delivered a strong late flourish to lift the Proteas to 187, setting India a stiff target of 188. The chase unravelled almost instantly when the in-form Ishan Kishan fell for a duck. India never recovered. Partnerships were scarce, the required rate ballooned, and wickets tumbled steadily. Bowled out for 111, India slumped to a heavy 76-run loss, damaging their net run rate and leaving their Super 8 campaign hanging in the balance.


Gautam Gambhir faces heat after Axar Patel sits out IND vs SA T20 World Cup Super 8 match | Cricket News – The Times of India


Gautam Gambhir faces heat after Axar Patel sits out IND vs SA T20 World Cup Super 8 match | Cricket News – The Times of India
Axar Patel (right) sits out IND vs SA T20 World Cup Super 8 match (ANI Photos)

India captain Suryakumar Yadav revealed that the team went with the same playing XI for the Super 8 game against South Africa on Sunday, which meant vice-captain Axar Patel was left out again, with Washington Sundar keeping his spot. After losing the toss, Surya admitted he wanted to bat first but accepted the toss result, calling Axar’s omission a tough call.

Jay Shah: Kapil Dev deserves more credit for 1983 World Cup triumph

“I was actually looking to bat first, but it’s okay, and we’re happy to bowl first. It’s very harsh on Axar Patel, but we’re going with the same team – just a tactical decision, so no changes from the last game,” he said at the toss. The decision sparked strong reactions on social media, with many fans questioning Axar’s exclusion.“Can someone tell me, why Axar Patel is dropped with his OG T2OI performances?” One fan wrote on X.“I have another question, can somebody tell me why Washington Sundar is not bowling to David Miller, if he was selected over Axar with lefties excuse?Does anything make sense under Gambhir?”Similar sentiments among fans over the Axar Patel omission call followed.In the match, South Africa had a shaky start after opting to bat. Jasprit Bumrah and Arshdeep Singh struck early, reducing them to 20/3 in just four overs. However, David Miller and Dewald Brevis staged a strong comeback, attacking India’s bowlers and shifting the momentum.Miller took on Varun Chakravarthy and Arshdeep Singh with powerful boundaries, while Brevis joined in with aggressive shots against Washington Sundar and others. The pair added quick runs and pushed the scoring rate up, helping South Africa recover to 84/3 at the halfway stage. Nevertheless, South Africa posted a strong total of 187/7 in their 20 overs after choosing to bat against India. After losing early wickets, Miller (63 off 35) and Brevis (45 off 29) led a crucial recovery, while Stubbs (44* off 24) provided a late surge. Bumrah was the standout bowler with 3/15, supported by Arshdeep’s 2/28, but India still face a challenging chase.