Loading…

OSI Systems (OSIS) backlog: remaining performance obligations

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

Data as of .

OSI Systems backlog history

$0$500M$1B$2BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025Jun 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$2.00M$1.80B0.0 yrs$91.1M
30 Jun 2026$1.80M$1.79B0.0 yrs$91.0M
31 Mar 2026$877M$1.81B0.5 yrs$89.4M
31 Dec 2025$625M$1.80B0.3 yrs$93.2M
30 Sep 2025$876M$1.75B0.5 yrs$75.2M
30 Jun 2025$820M$1.71B0.5 yrs$77.8M
31 Mar 2025$822M$1.69B0.5 yrs$74.9M
31 Dec 2024$776M$1.65B0.5 yrs$66.2M
30 Sep 2024$805M$1.60B0.5 yrs$56.9M
30 Jun 2024$836M$1.54B0.5 yrs$46.9M
31 Mar 2024$925M$1.47B0.6 yrs$45.8M
31 Dec 2023$928M$1.37B0.7 yrs$37.7M

Questions

What is OSI Systems's backlog?
OSI Systems reported $2.00M of remaining performance obligations at 30 Sep 2026, down 100% from a year earlier and up 11% from the previous quarter. That is 0.0 years of trailing revenue already under contract. Book-to-bill last quarter: 1.00.
How fast does OSI Systems's backlog turn into revenue?
Over the last twelve months OSI Systems recognised revenue equal to about 206% 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.