Loading…

Verisk Analytics (VRSK) backlog: remaining performance obligations

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

Data as of .

Verisk Analytics backlog history

$0$1B$2B$3BDec 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$526M$3.18B0.2 yrs$526M
30 Jun 2026$582M$3.14B0.2 yrs$582M
31 Mar 2026$690M$3.10B0.2 yrs$690M
31 Dec 2025$446M$3.07B0.1 yrs$446M
30 Sep 2025$507M$3.03B0.2 yrs$507M
30 Jun 2025$672M$2.99B0.2 yrs$672M
31 Mar 2025$592M$2.93B0.2 yrs$592M
31 Dec 2024$451M$2.88B0.2 yrs$451M
30 Sep 2024$502M$2.82B0.2 yrs$502M
30 Jun 2024$576M$2.78B0.2 yrs$576M
31 Mar 2024$639M$2.73B0.2 yrs$639M
31 Dec 2023$375M$2.68B0.1 yrs$375M

Questions

What is Verisk Analytics's backlog?
Verisk Analytics reported $526M of remaining performance obligations at 30 Sep 2026, up 4% from a year earlier and down 10% from the previous quarter. That is 0.2 years of trailing revenue already under contract. Book-to-bill last quarter: 0.93.
How fast does Verisk Analytics's backlog turn into revenue?
Over the last twelve months Verisk Analytics recognised revenue equal to about 585% 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.