Loading…

BETA Technologies (BETA) backlog: remaining performance obligations

How much revenue BETA Technologies already has under contract, how fast it converts, and who it is with.

Data as of .

BETA Technologies backlog history

$0$20M$40MSep 2025Dec 2025Mar 2026Jun 2026Sep 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Sep 2026$28.9M$53.6M0.5 yrs$20.1M
30 Jun 2026$33.0M$44.8M0.7 yrs$21.9M
31 Mar 2026$25.1M$36.1M0.7 yrs$17.1M
31 Dec 2025$14.3M$35.6M0.4 yrs$16.3M
30 Sep 2025$18.7Mn/an/a$16.0M

Questions

What is BETA Technologies's backlog?
BETA Technologies reported $28.9M of remaining performance obligations at 30 Sep 2026, up 55% from a year earlier and down 12% from the previous quarter. That is 0.5 years of trailing revenue already under contract. Book-to-bill last quarter: 0.77.
How fast does BETA Technologies's backlog turn into revenue?
Over the last twelve months BETA Technologies recognised revenue equal to about 242% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.