MCBRIDE PLC (MCB.L)

Every figure this model derived for MCB.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-06-30.

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	20,000,000	`PurchaseOfPropertyPlantAndEquipmentClassifiedAsInvestingActivities`	2025-06-30
cash	34,200,000	`CashAndCashEquivalents`	2025-07-01
current assets	300,500,000	`CurrentAssets`	2025-07-01
current liabilities	311,800,000	`CurrentLiabilities`	2025-07-01
equity	94,300,000	`Equity`	2025-07-01
interest expense	11,200,000	`FinanceCosts`	2025-06-30
ocf	63,100,000	`CashFlowsFromUsedInOperatingActivities`	2025-06-30
revenue	926,500,000	`Revenue`	2025-06-30
sbc	1,600,000	`AdjustmentsForSharebasedPayments`	2025-06-30

The ratios

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

Ratio	Value
cash operating margin	6.67
current ratio	0.96
current ratio reported	0.96
ev ebit	6.56
ev owner earnings	9.51
ev sales	0.43
fcf margin	4.65
interest cover	5.38
net debt ebitda	0.45
operating margin	6.5
owner earnings margin	4.48
revenue growth	-0.89
revenue growth per share	-0.89
roic	39.17
rule of 40	5.61
sbc pct revenue	0.17

What to be careful about

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

revenue is annual, not TTM
operating income is annual, not TTM
share count is from 2025-06-30 (425 days old, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
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`
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
2 of 5 dimensions could not be measured (durability, growth -- 30% of the model), so this row is not comparable with the others; its total rests on what was left