Write & Earn
Notifications

5 overs in cricket that never seemed to end

The bowlers who delivered these overs looked to have completely lost the plot.

Hardik Pandya bowled an 11-ball over on his T20I debut

Bowlers always have a key role to play in the success or failure of a particular team. Throughout the history of cricket, sides with a stronger bowling unit are the ones who have managed to dominate the scene. So whether it is the West Indies team of the 1970s and 1980s or the Australian team from the late 1990s and early 2000s, they had a bunch of outstanding bowlers to do the job.

However, even the best of bowlers can have bad days and there are some dubious records held by the finest among them. The worst it can get for a bowler, though, is when he concedes too many extras in an over and is forced to bowl an extended over. There have been numerous such instances in the different forms of cricket but there are some that really break the barriers.

Here are 5 instances in cricket when an over didn’t seem to end:

5. Daryl Tuffey (New Zealand) – 14-ball over against Australia in an ODI

Skipper Fleming tries to help Tuffey out

Former New Zealand fast bowler Daryl Tuffey represented his country in both Tests as well as ODIs and did a decent job with 77 and 98 wickets respectively. However, there is an unfortunate bowling feat which stayed stuck with him till the end of his career. Tuffey once bowled a 14-ball over in an ODI match against the Australians in 2005.

It was the first match of the over and Adam Gilchrist was at the striker’s end. None of his first six balls of the over were legitimate deliveries and by the time he bowled his first, the Kiwi pacer had already given away 14 runs. The rest of his over saw Daryl Tuffey bowl another couple of wides that pushed his tally up to 14 balls.

Considering the fact that Tuffey had already conceded 14 runs off his first ball, he did a pretty good job of giving away just 2 more runs in the rest of his over.

Page 1 of 5 Next
Fetching more content...