From equipment value to net recovery
An equipment price, an accounting value and a lender's net recovery answer different questions.
Build a net-recovery bridge
Net proceeds before priority allocation
3-unit shortfall to principal.
Assumptions & calculation
Net proceeds = gross sale − realisation and carrying costs. A negative value represents a cash requirement.
Original InfraCompute hypothetical model. All monetary inputs use one consistent, unspecified currency; m means millions. Values are not market quotes, appraisals or recommended financing terms. Inputs are not saved.
Define the asset and the denominator
A percentage residual is incomplete without its price basis. Ten per cent of a manufacturer's original list price can be very different from ten per cent of a discounted purchase invoice. State the exact hardware configuration, valuation date, currency and denominator alongside every residual assumption. Separate hardware from software, installation and prepaid services that may not transfer to a buyer.
American Compute's June 2026 residual report measures its published bands against original MSRP and anchors technology age to first commercial shipment. The report's transaction database and projections belong to American Compute. InfraCompute has not independently inspected that underlying dataset. Its published ranges should be identified as dated source estimates, rather than recreated as our own price index.
Use a recovery bridge
Start with an indicated gross sale price for the specified equipment. Deduct the costs and time required to realise it: diagnostics, repairs, data sanitisation, de-installation, transport, remarketing and any applicable obligations. Interest and facility costs may continue during the sale period. The amount available to the lender also depends on valid priorities and the transaction's legal structure.
Consider a hypothetical loan with 40 units of principal outstanding. A gross sale indication of 45 units appears to cover it. If realisation and carrying costs total eight units, only 37 remain before priority allocation. The resulting three-unit gap is an illustrative calculation, not a current GPU valuation. It shows why a modest gross cushion can disappear.
Stress the joint failure
A customer default may coincide with weaker demand for the equipment. Use a case where cash receipts and resale bids fall together, then extend the recovery period. A low price with an immediate sale can still be less severe than a similar price reached after months of unfunded costs. Keep these assumptions separate so the source of the shortfall is visible.
Also test the next buyer's constraints. Hardware can remain technically capable while losing economic appeal because the buyer lacks suitable power, cooling, software support or a workload that needs its memory configuration. A benchmark improvement in new silicon does not mechanically determine the resale discount for every older system.
Treat protection as another exposure
A residual guarantee or insurance policy adds a counterparty, conditions, claim timing and exclusions. Show covered and uncovered outcomes separately. Do not subtract an indicative insured amount from the balloon until eligibility, trigger dates and the disposal process are understood. Refresh the recovery bridge when hardware, location or the expected exit date changes; a book depreciation schedule cannot substitute for that work.
Questions for the credit paper
- Is the residual expressed against MSRP or actual purchase cost?
- Which costs sit between a bid and lender proceeds?
- What happens if revenue and equipment bids weaken together?
- Does protection cover this exit date and disposal route?
About this guide
Original InfraCompute analysis informed by the American Compute material below. The article structure, examples and interactive visuals are InfraCompute’s work. Source-specific findings remain attributed to American Compute; attribution does not imply affiliation or endorsement.
- American Compute, GPU Residual Value Report 2026 ↗
June 2026 residual-value report. The source’s underlying proprietary transaction data was not independently reviewed.
We reviewed the published edition and selected public references. We have not independently verified American Compute’s proprietary datasets, every market claim or confidential financing terms. Frameworks and hypothetical models describe questions to investigate; they do not establish protections in a particular financing. Legal and engineering conclusions depend on the relevant documents, system and jurisdiction.
Read our research methodology →