Loading…

Keysight Technologies (KEYS) backlog: remaining performance obligations

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

Data as of .

Keysight Technologies backlog history

$0$2B$4B$6BOct 2022Apr 2023Oct 2023Apr 2024Oct 2024Apr 2025Oct 2025Apr 2026Jul 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
31 Jul 2026$616M$6.58B0.1 yrs$957M
30 Apr 2026$660M$6.09B0.1 yrs$988M
31 Jan 2026$663M$5.68B0.1 yrs$966M
31 Oct 2025$629M$5.38B0.1 yrs$884M
31 Jul 2025$529M$5.24B0.1 yrs$765M
30 Apr 2025$557M$5.11B0.1 yrs$830M
31 Jan 2025$550M$5.02B0.1 yrs$803M
31 Oct 2024$576M$4.98B0.1 yrs$767M
31 Jul 2024$570M$5.00B0.1 yrs$744M
30 Apr 2024$580M$5.17B0.1 yrs$789M
31 Jan 2024$604M$5.34B0.1 yrs$805M
31 Oct 2023$581M$5.46B0.1 yrs$757M

Questions

What is Keysight Technologies's backlog?
Keysight Technologies reported $616M of remaining performance obligations at 31 Jul 2026, up 16% from a year earlier and down 7% from the previous quarter. That is 0.1 years of trailing revenue already under contract. Book-to-bill last quarter: 0.98.

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.