Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Sep 27, 2018, 09:55 AM (IST)
Edited: Sep 27, 2018, 09:55 AM (IST)
Few expected Durham to lose their final match of the 2018 County Championship, against Middlesex at Chester-le-Street. The target, after all, was a mere 167, and they were 45 for 1 at one stage. Then all went wrong: only 54 more were added as Durham slumped to a 57-run defeat. Paul Collingwood, in the last match for Durham, was bowled for 10 by a straight, short-pitched ball from Martin Anderssen that did not rise.
Collingwood had scored 32 in the first innings, and got Sam Robson and Dawid Malan in the Middlesex second innings. It could have been a fitting farewell for the captain, but Durham squandered a massive first-innings lead of 189. The Durham wickets were shared by Tim Murtagh, Ethan Bamber, James Fuller, and Anderssen.
“It was not quite the fairytale ending I was hoping for. It’s 23 years, I do feel a little bit sad. It’s the right time. I’ve put all my efforts into it and everybody only has a certain shelf life. I’m very satisfied and content with what I have achieved in the game. Hopefully the club will keep moving forward,” said Collingwood, as quoted by ESPNCricinfo.
“It has been a really surreal week. All the good luck messages and thank-you messages, it takes your breath away. Not the fairytale ending I was hoping for, but I can still have a smile on my face going into retirement after putting all my effort into it.”
Brief scores:
Middlesex 121 (James Harris 31; Matt Salisbury 6 for 37, Mark Wood 3 for 23) and 355 (Nick Gubbins 91, Stevie Eskinazi 96; Mark Wood 5 for 94) beat Durham 310 (Gareth Harte 112, Michael Richardson 50; Tim Murtagh 4 for 56, Ethan Bamber 3 for 78) and 109 (Cameron Steel 23, Stuart Poynter 23; Tim Murtagh 3 for 29) by 57 runs.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.