Gemini Q2 Revenue Surges 37% Yet Net Loss Hits $108M Amid Fraud Provisions

Key Takeaways

Gemini reported Q2 revenue growth of 37% to $45.5M, offset by a $107.7M net loss driven by a $16.1M credit fraud provision and rising operating expenses, causing stock volatility.

Woofun AI reports that Gemini's second-quarter results revealed a stark divergence between top-line expansion and bottom-line contraction, with a 37% revenue surge failing to offset a $107.7 million net loss, triggering immediate stock price volatility.

The revenue architecture shifted significantly as exchange trading weakened, causing exchange revenue to fall 38% to $12.5 million while trading volume dropped to $3.8 billion from $11.3 billion. Conversely, services revenue climbed 149% to $23.5 million, propelled by a 231% increase in credit card revenue to $16.2 million and a 50% rise in staking revenue to $4 million. Including interest income, services revenue and interest income totaled $26 million, highlighting the growing reliance on non-trading streams.

Woofun AI data shows this structural pivot was necessary to counterbalance the decline in core exchange activity.

Loss drivers were dominated by a $16.1 million provision for credit losses tied to an identity fraud event involving the credit card portfolio, which pushed transaction losses to $20.1 million from $3.6 million a year earlier. Gemini stated this elevated provision was concentrated among affected accounts and did not reflect broader deterioration in the portfolio. Operating expenses rose 24% year-over-year to $122.4 million, though they fell 15% from the first quarter as the company continued cost-cutting measures announced earlier this year.

Market reaction remained volatile following the disclosure; the stock price rose 3% during regular trading on Thursday, but fell nearly 5% in pre-market trading on Friday following the earnings release. This pattern underscores the market's sensitivity to fraud-related provisions despite operational efficiency gains.

Comments

Me
Replying to @User
0/800

No comments yet.

Notifications

Sign in to view messages
View all messagesManage subscriptions