Every figure this model derived for RYC.F, 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-10-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
cash
37,024,000,000
CashAndCashEquivalents
2025-11-01
equity
139,092,000,000
EquityAttributableToOwnersOfParent
2025-11-01
interest expense
70,825,000,000
InterestExpense
2025-10-31
ocf
55,220,000,000
CashFlowsFromUsedInOperatingActivities
2025-10-31
revenue
66,605,000,000
Revenue
2025-10-31
The ratios
The figures themselves rather than their scores — what somebody looking up
RYC.F on one particular measure came for.
Ratio
Value
fcf margin
82.91
owner earnings margin
82.91
revenue growth
16.15
revenue growth per share
16.15
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about RYC.F's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
no operating income found in XBRL
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no current capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
reports in CAD while its share price is quoted in EUR, and no exchange rate could be used (no rate for EUR to CAD that is less than 30 days old, and this is not a refresh). Every multiple would pair one currency with another, so none of them is a ratio — set `market_cap` in overrides.yaml in CAD to score it
share count is from 2025-10-31 (303 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`
quality DROPPED from the total: only 2 of 5 inputs could be computed (operating margin, roic, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev ebit, 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
resilience DROPPED from the total: only 1 of 3 inputs could be computed (interest cover, liquidity 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
5 of 5 dimensions could not be measured (quality, valuation, durability, resilience, growth -- 100% of the model), so this row is not comparable with the others; its total rests on what was left