Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Jul 12, 2016, 01:10 AM (IST)
Edited: Jul 12, 2016, 08:43 AM (IST)
West Indies wicketkeeper-batsman, Denesh Ramdin, has been sanctioned by West Indies Cricket Board (WICB) for showing dissatisfaction for being dropped from the squad for the four-match Test series against India, starting from July 21. The right-handed batsman used the social media platform, Twitter, to express his disappointment over being ignored for the all-important series against India, led by Virat Kohli. Ramdin being for his national team in their last series in the longer format against Australia in 2015. Ramdin had a decent outing with the bat in Australia where he also scored a century and depicted his record in Tests and the berserk logic of the West Indian selectors in his tweet. This was in breach of the WICB policy and the terms of his retainer contract. As a consequence, Ramdin has since been sanctioned. ALSO READ: West Indies announce 12-man squad for Tests against India
According to windiescricket.com, Ramdin has represented West Indies in 74 Tests and has scored four centuries along with fifteen fifties to his name. He has an average of 25.87 in the longer format and been effective with his wicketkeeping gloves as well. He has taken 205 catches and affected 15 stumping during his stint with the team, so far. ALSO READ: Taylor announces retirement from Tests
The West Indies team have been on a roll in the shortest format of the game but have a long way to go while playing in whites. The selectors have taken a lot of new faces for the home series against India and will like to start the rebuilding process of their team with this series as well. Ramdin’s outbursts showed his frustrations with the board who have been in the loggerheads with their players since time immemorial and this has just added one more episode to it.
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.