What is RPC's backlog?

RPC reported $1.40M of remaining performance obligations at 31 Mar 2025, up 133% from a year earlier. That is 0.0 years of trailing revenue already under contract.

RPC (RES) backlog: remaining performance obligations

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

Data as of 7 Nov 2026.

Open the interactive Backlog view RPC competitor analysis

RPC reported $1.40M of remaining performance obligations at 31 Mar 2025, up 133% from a year earlier. That is 0.0 years of trailing revenue already under contract.
Customer prepayments (contract liabilities) cover 100.0% of the backlog.
Twelve-month book-to-bill: 1.00, i.e. 1.00 of new orders for every 1 of revenue recognised.
Backlog growth minus revenue growth: +143 points — orders are running ahead of revenue.
The latest filed figure is more than 200 days old.

RPC backlog history

Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).

Amounts in USD. Source: SEC XBRL filings.
Quarter end	Backlog (RPO)	TTM revenue	Coverage	Customer prepayments
31 Mar 2025	$1.40M	$1.37B	0.0 yrs	$1.40M
31 Mar 2024	$600,000	$1.52B	0.0 yrs	$600,000

Questions

What is RPC's backlog?: RPC reported $1.40M of remaining performance obligations at 31 Mar 2025, up 133% from a year earlier. That is 0.0 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.