SPIRE HEALTHCARE GROUP PLC (SPI.L)

Every figure this model derived for SPI.L, the value it took, and the element in the company's own XBRL it was read from — so any of it can be checked against the filing rather than taken on trust. As at 2025-12-31.

The figures, and where each came from

This is the part no other screener shows. Each figure below names the XBRL element it was read from, so it can be checked against the filing itself.

Figure	Value	XBRL tag	As at
capex	76,300,000	`PurchaseOfPropertyPlantAndEquipmentClassifiedAsInvestingActivities`	2025-12-31
cash	34,700,000	`CashAndCashEquivalents`	2026-01-01
current assets	221,500,000	`CurrentAssets`	2026-01-01
current liabilities	346,800,000	`CurrentLiabilities`	2026-01-01
equity	742,800,000	`EquityAttributableToOwnersOfParent`	2026-01-01
interest expense	105,000,000	`FinanceCosts`	2025-12-31
ocf	242,200,000	`CashFlowsFromUsedInOperatingActivities`	2025-12-31
revenue	1,579,800,000	`Revenue`	2025-12-31
sbc	0	`AdjustmentsForSharebasedPayments`	2022-12-31

The ratios

The figures themselves rather than their scores — what somebody looking up SPI.L on one particular measure came for.

Ratio	Value
cash operating margin	7.76
current ratio	0.64
current ratio reported	0.64
fcf margin	10.5
interest cover	1.17
net debt ebitda	2.69
operating margin	7.76
owner earnings margin	10.5
revenue growth	4.54
revenue growth per share	4.54
roic	9.03
rule of 40	12.3
sbc pct revenue	0.0

What to be careful about

What this model itself distrusts about SPI.L's figures. Written by the derivation as it ran, not added afterwards.

revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged (last tagged 2022-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
no forward EPS estimate; growth rests on filings only. Analyst consensus is not published in XBRL, so it has to be fetched from a data provider or set by hand in overrides.yaml as `eps_growth_2y`
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev sales, ev owner earnings not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
durability DROPPED from the total: only 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth DROPPED from the total: only 1 of 4 inputs could be computed (sustained growth, margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (valuation, durability, growth -- 55% of the model), so this row is not comparable with the others; its total rests on what was left