Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Jan 14, 2016, 04:21 PM (IST)
Edited: Jan 16, 2016, 12:27 AM (IST)
Former South Africa and Highveld Lions batsman Gulam Bodi has been revealed to be the cricketer under investigation for the match-fixing reports in Ram Slam T20 that emerged earlier. Bodi has been called the ring leader by the Afrikaans newspaper that made the startling revelation. Earlier in a press release, Cricket South Africa (CSA) had said the cricketer had been charged under its anti-corruption code as an intermediary with “contriving to fix, or otherwise improperly influence aspects” of the 2014/15 domestic Twenty20 competition. The publication that said Bodi was involved in the said scandal is called Netwerk24. Bodi has retired from cricket last year. ALSO READ: Former South African cricketer caught in match-fixing
“The intermediary has been charged with contriving to fix, or otherwise improperly influence aspects of the 2015 Ram Slam T20 Challenge Series and with failing or refusing, without compelling justification, to co-operate with an investigation carried out by CSA’s Designated Anti-Corruption Official,” the CSA statement had earlier said in regards to the matter.
The cricketer who played two One-Day Internationals (ODIs) and one Twenty20 International (T20I) for South Africa in the year 2007 was approached by Netwerk24 for comment on the issue. But the batsman bluntly turned down the offer to accept or refute the claims. “No, absolutely no comment. Sorry,” were Bodi’s exact words.
It was further added in the report that while CSA were against naming the perpetrator, as many as three sources closely privy to the investigation had confirmed that the suspected ringleader was Bodi. CSA has refused to give further comment on the issue.
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.