Loading…

Mercury Systems (MRCY) backlog: remaining performance obligations

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

Data as of .

Mercury Systems backlog history

$0$500M$1BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025ul 2026ct 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
2 Oct 2026$1.19B$1.01B1.2 yrs$152M
3 Jul 2026$1.08B$984M1.1 yrs$151M
27 Mar 2026$860M$967M0.9 yrs$128M
26 Dec 2025$824M$942M0.9 yrs$137M
26 Sep 2025$783M$933M0.8 yrs$126M
27 Jun 2025$788M$912M0.9 yrs$128M
28 Mar 2025$723M$888M0.8 yrs$143M
27 Dec 2024$770M$884M0.9 yrs$136M
27 Sep 2024$766M$859M0.9 yrs$96.9M
28 Jun 2024$768M$835M0.9 yrs$74.4M
29 Mar 2024$794Mn/an/a$71.2M
29 Dec 2023$658Mn/an/a$81.6M

Questions

What is Mercury Systems's backlog?
Mercury Systems reported $1.19B of remaining performance obligations at 2 Oct 2026, up 52% from a year earlier and up 10% from the previous quarter. That is 1.2 years of trailing revenue already under contract. Book-to-bill last quarter: 1.44.
How fast does Mercury Systems's backlog turn into revenue?
Over the last twelve months Mercury Systems recognised revenue equal to about 116% 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.