AST SpaceMobile Is Impossible to Ignore Right Now. Here's What to Do With It.

AST SpaceMobile reported 2025 revenue of $70 million, up from $4 million in 2024, with service revenue rising to $26.5 million from $3.9 million. The company is making progress on its space-based broadband network and expects satellite launches every one to two months in 2026, but it still faces substantial capital spending and is not likely to be sustainably profitable soon. The article is more of a valuation and risk discussion than a new catalyst, though it highlights a 280% share gain over the past year and a recent pullback of more than one-third from January highs.

Analysis

ASTS is transitioning from a concept story to a deployment story, but the market is still pricing it like a finished network rather than an asset-formation business. The key second-order dynamic is that every incremental satellite launch can expand the addressable service footprint before the company is anywhere near full-scale profitability, so revenue momentum can stay ahead of earnings power for several quarters. That creates a classic “good business, bad cash conversion” setup where operating leverage is real but lags the headline growth.

The main beneficiaries are the incumbent telecom partners, which gain a differentiated coverage layer without funding the capex burden, and potentially equipment / launch providers that get a multi-year order stream. The likely losers are capital-efficient growth names and some lower-quality telecom substitutes that lose the narrative advantage if ASTS proves that satellite-to-phone can monetize through existing distribution. A less obvious winner could be defense-adjacent investors: a functioning low-earth-orbit direct-to-device network has dual-use implications, and that optionality can support valuation even if commercial profitability remains distant.

Consensus seems to be underestimating how financing risk, not technology risk, will drive the next leg. If launches accelerate into a cadence of every 4-8 weeks, the stock can rerate on milestones; if any launch slip or regulatory/partner delay hits, the equity can de-rate violently because the market is funding the buildout with future expectations rather than current cash flow. Over 6-18 months, the critical variable is whether service revenue inflects faster than dilution and capex burn.

Contrarianly, the drawdown may be more of a valuation reset than a broken thesis: the market likely moved from pricing in near-term scarcity value to pricing in execution risk. That means ASTS can still work, but the expected return is now dominated by entry price and position sizing rather than conviction alone. In this setup, the clean trade is not blind longs; it is buying only when volatility compresses after launch milestones or selling premium against the buildout cycle.

Key Decisions for Investors

• Avoid chasing ASTS after strength; wait for post-launch pullbacks or failed-rally entries. The risk/reward is poor if the stock is re-rating on narrative rather than cash flow, and downside can widen sharply on any cadence miss.
• For existing ASTS holders, trim 25-50% into strength and let the remainder run. The stock still has multi-year upside, but the position should be sized as a venture-style satellite on a core book, not a full-sized fundamental long.
• If seeking a relative-value expression, prefer long T or VZ against ASTS on any hype-driven spikes. The telecom partners capture option value with materially lower execution and financing risk, making them the better risk-adjusted way to play direct-to-device adoption.
• Consider selling cash-secured puts on ASTS only after launch windows, with 2-4 month maturities. That captures elevated implied volatility while using time as the edge; invalidation is a sequence of launch delays or partner slippage.
• Set a tactical alert for any guidance update on launch cadence or service revenue acceleration. A confirmed monthly-to-biweekly satellite cadence would justify adding exposure; a slip should trigger a reduction because the equity is highly sensitive to execution timing.