According to Bloomberg, the Chinese ride-hailing giant DiDi has been asked by the country’s regulators to come up with a plan to delist from the US market
Because of concerns regarding leakage of sensitive data, the report said the Cyberspace Administration of China wants DiDi to work out the details for a delisting subject to government approval. According to the same information, DiDi could either go for privatization or a listing in Hong Kong following the delisting. In case of privatization, DiDi will be priced at $14/share, and a Hong Kong float would likely be at a discount to what its shares were trading at in the US.
A state-directed delisting would mark an unprecedented move highlighting Beijing’s crackdown on giant tech companies and put them under tighter regulation. DiDi is targeted in this situation because, shortly after its US listing, regulators opened a cybersecurity review into the company. DiDi caught regulators’ eyes after pushing ahead with the IPO even though it didn’t resolve the outstanding cybersecurity issues that authorities wanted to solve.
At the moment of writing, during pre-market trading, DiDi stock price was trading 6.04% lower.
Sources: Bloomberg.com, cnbc.com, finance.yahoo.com
This information is prepared for general circulation. It does not have regard to the specific investment objectives, financial situation or the particular needs of any recipient.
You should independently evaluate each financial product and consider the suitability of such a financial product, by taking into account your specific investment objectives, financial situation or particular needs, and by consulting an independent financial adviser as needed, before dealing in any financial products mentioned in this document.
This information may not be published, circulated, reproduced or distributed in whole or in part to any other person without the Company’s prior written consent.
Past performance is not always indicative of likely or future performance. Any views or opinions presented are solely those of the author and do not necessarily represent those of sc.capex.com