Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Jul 09, 2014, 04:20 PM (IST)
Edited: Jul 09, 2014, 04:20 PM (IST)
Jul 9, 2014
England pace spearhead James Anderson on Wednesday became the first bowler to complete 50 wickets at Nottingham, Trent Bridge. The right-arm pacer achieved the feat when he had India openerShikhar Dhawan caught by wicketkeeper Matt Prior in the first session’s play of the first day at the venue.
Even on a slow wicket, with no movement in the air, Anderson used the angles rather than movement. He looked distinctly unhappy, but has still been a handful at Trent Bridge..
Dhawan fell after scoring 12 off 24 balls. The Indian opener did not look comfortable the crease and fell in the seventh over of the day. He was troubled by the bounce and pace generated by England pacer Stuart Broad as well.
Few days ago, Anderson went onto take 350 Test wickets for his country, while playing against Sri Lanka in the first Test at Lord’s. He became the second bowler after Ian Botham from England to take 350 wickets in Tests. He took the wicket off Angelo Mathews to achieve the milestone. Anderson is also second in the list in terms of wickets being taken at Lord’s. Botham heads the list again.
Anderson made his Test debut against Zimbabwe back in 2003 at Lord’s at the age of just 20. He took a five-wicket in his first Test. Since then, he has gone onto play 92 Tests for his country. Anderson has picked up 15 five-fors and two 10-fors in his Test career. His best figures in a match came against Pakistan at Trent Bridge in 2010.
Most wickets at Trent Bridge:
Overall | ||
W | Ave | |
James Anderson | 50 | 17.72 |
Alec Bedser | 41 | 20.21 |
Fred Trueman | 32 | 16.5 |
Shane Warne | 29 | 17.72 |
Brian Statham | 28 | 22.85 |
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.