It’s been over a month and a half since Sushant Singh Rajput passed away but the mystery around his death is only getting deeper by the day. Several conspiracy theories are doing the rounds on the internet with many suspicions being raised on who could be responsible for the 34-year-old actor’s sudden death. More recently, Sushant’s father K.K. Singh moved to Bihar Police and filed an FIR against Sushant’s girlfriend Rhea Chakraborty for abetment of suicide, cheating, theft among other charges.

The Bihar Police arrived in the city on July 28 and have been re-investigating the evidences gathered by the Mumbai Police. This has further led to creating furor on social media with people backing Bihar Police and questioning Mumbai Police over its investigation


With so many assumptions and speculations being made on the internet, Param Bir Singh, the Mumbai Police Commissioner, finally decided to break his silence and issue a clarification on Sushant’s death case today. He called the press and elaborated on how sincerely the team has been conducting the investigation so far by ‘not sparing anyone.’ While he spoke about all the events that took place since Sushant’s demise, he also mentioned about looking into Sushant’s Google history after accessing his laptop, phone.

“So far on the basis of what we have examined through his Google history, he used to examine painless death, bipolar disorder. He would keep searching his name on Google. We have also learnt that when his name got linked to Disha Salian’s suicide, he was very emotionally disturbed”, said the Commissioner in his statement.

The Commissioner also claimed that Sushant’s father or his family members had not raised any suspicion against anyone when they had recorded their first statement on June 16, two days after Sushant’s death. He also clarified that contrary to the allegations by his family that 15 crore has been missing from Sushant’s account, there’s no transfer being made to Rhea’s account as claimed in the FIR.

It’s left to see what turn does this case hereafter.

error: Content is protected !!