Loading…

Kingsoft Cloud (3896.HK) backlog: remaining performance obligations

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

Data as of .

Kingsoft Cloud backlog history

$0$500M$1B$2BDec 2020Dec 2021Jun 2022Sep 2022Dec 2022Dec 2023Dec 2024Dec 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 Dec 2025$27.4M$1.37B0.0 yrs$38.7M
31 Dec 2024$6.30M$1.07B0.0 yrs$34.1M
31 Dec 2023$9.50M$993M0.0 yrs$61.2M
31 Dec 2022$13.6M$1.19B0.0 yrs$59.7M
30 Sep 2022$11.3Mn/an/a$57.9M
30 Jun 2022$7.70Mn/an/a$56.1M
31 Dec 2021$8.10M$1.42B0.0 yrs$59.5M
31 Dec 2020$2.00M$1.01B0.0 yrs$29.3M

Questions

What is Kingsoft Cloud's backlog?
Kingsoft Cloud reported $27.4M of remaining performance obligations at 31 Dec 2025, up 335% 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.