Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Sep 14, 2016, 10:22 AM (IST)
Edited: Sep 14, 2016, 10:22 AM (IST)
Former South Africa wicketkeeper-batsman Thami Tsolekile has been arrested for assaulting a 14-year-old minor boy at Cape Town, near Pinelands High School. Tsolekile as a resulted was arrested on September 8. Tsolekile, who was most recently banned for 12 years for trying to fix six RamSlam T20 2015 matches has denied all charges and in fact insisted that the boy had pelted stones at his car. Tsolekile has been formally charged with common assault and made his first appearance in a local Court, which was his first appearance in a local court on September 13 for the first time since being arrested on September 8, according to cricbuzz.com. READ: Thami Tsolekile first cricketer named in South African match-fixing scandal investigation
Tsolekile played two Tests against India on the 2004 tour, at Kanpur and Kolkata. His last appearance for South Africa was against England in 2004 at Port Elizabeth. The cricketer from Western Province was centrally contracted with Cricket South Africa (CSA) as recently as 2013-14, and was even a part of the South African touring party to Australia in 2012.
According to The Guardian, Tsolekile is believed to have been paid at least R75,000 ($6,46) to improperly influence a match in last year’s Ram Slam tournament, which is the premier domestic Twenty20 tournament in the African country.
In that tournament, Tsolekile captained the Highveld Lions and could face at least a five-year ban if he is found guilty of malicious activities.Under the Prevention and Combating of Corrupt Activities Act, the wicketkeeper-batsman can also be criminally charged as the Act contains clause for sporting events. The law was passed in 2004, four years after Hansie Cronje was handed a life ban for his involvement in match-fixing.
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.