Every figure this model derived for M4M1.DE, 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
M4M1.DE on one particular measure came for.
Ratio
Value
cash operating margin
23.98
current ratio
0.82
current ratio reported
0.82
ebit cagr
35.17
ebit yoy
62.47
fcf margin
18.31
growth cv
2.1
interest cover
1.87
net debt ebitda
3.6
operating margin
23.12
owner earnings margin
17.45
revenue growth
2.53
revenue growth per share
2.53
roic
12.53
rule of 40
25.65
sbc pct revenue
0.86
What to be careful about
What this model itself distrusts about M4M1.DE'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 (606 days ago) - the tag chain found nothing recent, so treat this row as unscored
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
gross profit last tagged 2022-12-31 and no cost of sales line to rebuild it from; dropped from durability
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 2 of 4 inputs could be computed (contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left