News

Public · Published

Under the Radar: Tokenization Firm Securitize Surges on Revenue Gain — WSJ

Securitize reported third-quarter revenue of $18.6 million, up 13%, as tokenization revenue increased. It recorded a $66.3 million loss, compared with a $4.1 million profit a year earlier, mainly because of non-cash expenses and accounting charges tied to its public listing earlier this year.

Published:

Updated:

What happened

Securitize reported third-quarter revenue of $18.6 million, up 13%, as tokenization revenue increased. It recorded a $66.3 million loss, compared with a $4.1 million profit a year earlier, mainly because of non-cash expenses and accounting charges tied to its public listing earlier this year.

Confirmed

Global impact / market context

Revenue growth suggests traditional financial institutions are using Securitize’s blockchain-based service to put assets on digital networks. If that demand continues, it could support sales, but the quarterly loss shows that revenue growth has not yet translated into profit; listing-related charges accounted for much of the loss.

Analyst inference

The share rise followed stronger revenue and higher tokenization sales, while the reported loss reflected mainly non-cash and listing-related accounting costs. The stock nevertheless remained down 24% year to date, so Tuesday’s gain did not erase its earlier decline.

Confirmed

What to watch

  1. Check whether future results show continued growth in tokenization revenue, which would indicate that financial institutions are still adopting the service and supporting sales. Analyst inference
  2. Watch whether losses narrow as public-listing accounting charges fade; the article says those charges contributed to the third-quarter loss but gives no future outlook. Analyst inference
  3. Track whether revenue growth increasingly covers operating costs, since Securitize reported higher sales alongside a quarterly loss despite non-cash and listing-related charges. Analyst inference

Evidence

  • Original source link unavailable