LiveOne Inc reported Q1 Fiscal 2026 earnings with revenue falling short at $19.2 million, missing estimates of $21.02 million. The company faced a significant decline in Slacker revenues, leading to an operating loss of $4.0 million, up from $0.8 million in Q1 Fiscal 2025. Despite this, LiveOne Inc secured a $16.5 million deal with Amazon and entered a partnership with a Fortune 250 Streaming Network, expected to generate over $26 million in revenue.
LiveOne Inc. (LVO) has released its Q1 fiscal 2026 earnings report, showing a significant decrease in revenue and an increase in operating loss. The company reported revenue of $19.2 million, a decrease of $13.9 million from the same period last year, and an operating loss of $4.0 million, up from $0.8 million in Q1 fiscal 2025 [1].
The revenue decline was primarily attributed to reduced revenues from its Slacker division. Despite the revenue drop, LiveOne made strategic moves, including a 31% staff reduction and the expansion of B2B partnerships. Notably, the company secured a $16.5 million deal with Amazon through PodcastOne and a significant partnership with a Fortune 250 streaming network, expected to generate over $26 million in revenue [2].
LiveOne also completed a $10.2 million equity raise to support its Bitcoin yield strategy and Web3 initiatives. The company reported an adjusted EBITDA loss of $1.8 million compared to a positive $2.9 million last year. Despite these challenges, LiveOne is optimistic about future growth, with plans to launch a major live event series and explore merger and acquisition opportunities [1].
The management remains focused on building momentum through strategic partnerships and expanding its Web3 team, positioning the company for continued success in the evolving digital landscape.
References:
[1] https://www.tipranks.com/news/company-announcements/liveone-reports-q1-fiscal-2026-earnings
[2] https://www.marketscreener.com/news/liveone-lvo-reports-q1-fiscal-2026-revenue-of-19-2-million-eliminating-14-1-million-in-short-te-ce7c51dbdf8af32d
Comments

No comments yet