Loading…

Telos (TLS) backlog: remaining performance obligations

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

Data as of .

Telos backlog history

$0$100M$200MSep 2022Mar 2023Sep 2023Mar 2024Sep 2024Mar 2025Sep 2025Mar 2026Jun 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 Jun 2026$56.5M$194M0.3 yrs$17.2M
31 Mar 2026$61.9M$182M0.3 yrs$18.1M
31 Dec 2025$68.8M$165M0.4 yrs$11.2M
30 Sep 2025$65.5M$144M0.5 yrs$13.7M
30 Jun 2025$51.7M$117M0.4 yrs$13.0M
31 Mar 2025$51.4M$109M0.5 yrs$6.70M
31 Dec 2024$51.2M$108M0.5 yrs$6.80M
30 Sep 2024$38.9M$123M0.3 yrs$6.80M
30 Jun 2024$31.2M$135M0.2 yrs$5.80M
31 Mar 2024$36.1M$140M0.3 yrs$6.00M
31 Dec 2023$52.1M$145M0.4 yrs$6.70M
30 Sep 2023$79.0M$152M0.5 yrs$5.80M

Questions

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