South Africa’s T20 World Cup dream was brutally shattered on Wednesday night, and head coach Shukri Conrad didn’t mince words about it. It wasn’t just a loss—it was a merciless thrashing. After New Zealand handed them a nine-wicket defeat in the semifinal, Conrad’s raw honesty cut through the usual post-match clichés. But here’s where it gets controversial: when asked if his team had ‘choked’—a label South Africa has battled for decades—Conrad fired back, “I don’t know if tonight was a choke. I thought it was a bloody walloping. To choke, you’ve got to at least be in the game. We didn’t even get a sniff.”
And this is the part most people miss: New Zealand didn’t just win—they dominated with a level of precision that left South Africa reeling. Chasing 170, opener Finn Allen blazed an unbeaten century off just 33 balls, the fastest in tournament history, while Tim Seifert’s 58 off 33 balls sealed the deal in a mere 12.5 overs. Conrad even turned to his native Afrikaans to describe the defeat, calling it a ‘snotklap’—a term for a sudden, unexpected smackdown. Ouch.
Earlier, New Zealand’s bowlers had set the tone, with Cole McConchie dismantling South Africa’s top order in the second over. Spinners then choked the middle order, leaving stars like Aiden Markram and David Miller struggling to find rhythm. A late surge from Marco Jansen (55 off 30) and Tristan Stubbs pushed South Africa to 169, but it was nowhere near enough. “They strangled us from the start,” Conrad admitted. “A lot went wrong, but credit to them—they were outstanding.”
Despite the crushing defeat, Conrad stood by his team, who entered the semifinal as the tournament’s only unbeaten side with seven straight wins. “We did exceptional things,” he said. “Not many thought we’d make it this far. I’m incredibly proud of these guys, even if it doesn’t feel like much now.”
But here’s the question that’ll spark debate: Was this truly a choke, or was South Africa simply outclassed by a superior opponent? And does the ‘chokers’ label still hold weight, or is it time to retire it? Let’s hear your thoughts in the comments—this is one conversation that’s far from over.
