Littler lands rare triple-bull checkout at Grand Slam
Summarised from 2 outlets · Updated 17 Nov, 01:13 · Archive
Luke Littler landed a rare triple-bull checkout at the Grand Slam of Darts in Wolverhampton despite losing his match.
Two-time defending champion Luke Littler has progressed to the last 16 of the Grand Slam of Darts in Wolverhampton despite losing his match 5-4 to Dutchman Niels Zonneveld. The 19-year-old had already secured the three legs needed to advance from the group stage before the final encounter.
With the pressure off, Littler showcased an audacious skill, landing a rare triple-bull checkout—a 150 finish using three bullseyes—to level the match at 4-4. Television footage appeared to capture Littler asking the crowd whether he should attempt the unorthodox finish before stepping up to play.
Zonneveld, whose elimination meant he had nothing to lose, was unbothered by the shot. 'I don't think it was disrespectful because I was 4-3 up, he was already through so could go for the three bullseyes,' Zonneveld said. 'It was brilliant ... I don't see it as disrespect.' He won the deciding leg, handing Littler his first ever defeat in the tournament.
Littler later tweeted about the moment, writing: 'Brain rot – didn't know if I was through or not … 3 bulls will do to definitely secure my spot in the next round.'

How it is being reported
- Defending champ sends fans wild with rare checkoutTwo-time defending champion Luke Littler has thrilled fans in Wolverhampton en route out of the Grand Slam of Darts group stage.The West Australian · 17 Nov, 00:42
- Defending champ sends fans wild with rare checkoutTwo-time defending champion Luke Littler has thrilled fans in Wolverhampton en route out of the Grand Slam of Darts group stage.Perth Now · 17 Nov, 00:42
In this story: Luke Littler · Niels Zonneveld · Grand Slam of Darts · Wolverhampton · Gerwyn Price · Alan Soutar
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)