Every figure this model derived for LIVA.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 2024-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.
The figures themselves rather than their scores — what somebody looking up
LIVA.F on one particular measure came for.
Ratio
Value
cash operating margin
9.42
current ratio
0.96
current ratio reported
0.96
ebit cagr
26.53
ebit yoy
41.88
fcf margin
4.62
growth cv
2.35
interest cover
9.06
net debt ebitda
1.22
operating margin
9.42
owner earnings margin
4.62
revenue growth
-0.81
revenue growth per share
-0.81
roic
22.3
rule of 40
8.61
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about LIVA.F's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2025-01-01 (1y old); this company's data is not usable and the scores below should be ignored
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2024-12-31 (605 days ago) - the tag chain found nothing recent, so treat this row as unscored
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
reports in USD and quotes in EUR, so the share price is converted at 1 EUR = 1.1650 USD as at 2026-08-28. Only the price is converted: every figure from the filing is as reported, and only the multiples built on market capitalisation carry the rate — but no share count is available, so there is still no market capitalisation
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 rests on 3 of 4 inputs; not tagged: contracted coverage