Loading…

Agilent Technologies (A) backlog: remaining performance obligations

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

Data as of .

Agilent Technologies backlog history

$0$2B$4B$6BJan 2019Jul 2019Jan 2020Oct 2021Oct 2023Oct 2025Backlog (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 Oct 2025$437M$6.95B0.1 yrs$803M
31 Oct 2024$409M$6.51B0.1 yrs$701M
31 Oct 2023$331M$6.83B0.0 yrs$616M
31 Oct 2022$357M$6.85B0.1 yrs$557M
31 Oct 2021$299M$6.32B0.0 yrs$519M
31 Oct 2020$217M$5.34B0.0 yrs$446M
31 Jan 2020$210M$5.24B0.0 yrs$432M
31 Oct 2019$207M$5.16B0.0 yrs$386M
31 Jul 2019$182M$5.09B0.0 yrs$391M
30 Apr 2019$174M$5.02B0.0 yrs$394M
31 Jan 2019$166M$4.99B0.0 yrs$393M

Questions

What is Agilent Technologies's backlog?
Agilent Technologies reported $437M of remaining performance obligations at 31 Oct 2025, up 7% from a year earlier. That is 0.1 years of trailing revenue already under contract.

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.