Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Feb 02, 2016, 12:27 AM (IST)
Edited: Feb 02, 2016, 01:11 PM (IST)
The joy of Nepal’s success in the ongoing ICC Under-19 Cricket World Cup 2016 came under threat when allegations were made by a Ranji Trophy cricketer, Kaustub Pawar, about their captain Raju Rijal indulging in age fraud. In a Facebook post Pawar said he had played with Rijal in the under-15 Mumbai team and the players of that batch were currently aged 24 and 25. Pawar implied that even Rijal belonged to a similar age group and had gotten through by committing age fraud. He accompanied his post with hashtags like ‘shame’ and ‘save cricket’. FULL SCORECARD: India vs Nepal, match NO. 18 of ICC Under-19 Cricket World Cup
Rijal responded to these allegations but was not very forceful in his reply. He only said he was not aware of the post in question as he is inactive on the sphere of social media. “I don’t have any idea about this. I am not in social media [As Pawar accused Raju via Facebook]. So I can not comment on this,” Rijal told Cricwizz. ALSO READ: Is Nepal Under-19 Captain Raju Rijal Actually 25?
Further research revealed that a player by the name of Raju Ramachandra Sharma has in fact played for Mumbai, albeit in the Under-15 age group in 2004-05 and 2005-06. The said Raju Sharma has even captained Mumbai Under-15s in certain Polly Umrigar fixtures.
However, in conflict with the official records of Raju Rijal which state he was born in Dhangadi Nepal, documents state that the Under-19 Mumbai cricketer Raju Sharma was born in Ramnagar Maharashtra. There is certain to be further investigation into the matter.
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.