Every figure this model derived for MATH, 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-03-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
MATH on one particular measure came for.
Ratio
Value
cash operating margin
40.83
current ratio
1.09
current ratio reported
1.09
dilution pct
11.08
ebit yoy
1209.63
fcf margin
0.06
growth cv
1.03
interest cover
231.74
operating margin
39.13
owner earnings margin
-1.64
revenue growth
165.86
revenue growth per share
139.34
roic
59.88
rule of 40
204.99
sbc pct revenue
1.69
What to be careful about
What this model itself distrusts about MATH's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2025-03-31 (517 days ago) - the tag chain found nothing recent, so treat this row as unscored
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-03-31 (152 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 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