Loading…

Aeva Technologies (AEVA) backlog: remaining performance obligations

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

Data as of .

Aeva Technologies backlog history

$0$20M$40MDec 2023Mar 2025Sep 2025Mar 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$26.1M$24.7M1.1 yrs$1.20M
30 Jun 2026$28.7M$21.6M1.3 yrs$1.80M
31 Mar 2026$31.4M$21.0M1.5 yrs$2.60M
31 Dec 2025$34.8M$18.1M1.9 yrs$2.90M
30 Sep 2025$42.4M$15.2M2.8 yrs$3.30M
30 Jun 2025$44.7M$13.8M3.2 yrsn/a
31 Mar 2025$47.3M$10.3M4.6 yrsn/a
31 Dec 2024$47.0M$9.10M5.2 yrs$0
31 Dec 2023$25.0M$4.30M5.8 yrsn/a

Questions

What is Aeva Technologies's backlog?
Aeva Technologies reported $26.1M of remaining performance obligations at 30 Sep 2026, down 38% from a year earlier and down 9% from the previous quarter. That is 1.1 years of trailing revenue already under contract. Book-to-bill last quarter: 0.61.
How fast does Aeva Technologies's backlog turn into revenue?
Over the last twelve months Aeva Technologies recognised revenue equal to about 74% 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.