Every figure this model derived for MAMK, 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
capex
56,877
PaymentsToAcquirePropertyPlantAndEquipment
2025-10-31
cash
122,381
CashAndCashEquivalentsAtCarryingValue
2025-10-31
current assets
21,544,654
AssetsCurrent
2025-10-31
current liabilities
6,893,868
LiabilitiesCurrent
2025-10-31
equity
12,283,787
StockholdersEquity
2025-10-31
interest expense
159,166
InterestExpense
2025-10-31
ocf
-5,285,745
NetCashProvidedByUsedInOperatingActivities
2025-10-31
revenue
29,220,846
Revenues
2025-10-31
The ratios
The figures themselves rather than their scores — what somebody looking up
MAMK on one particular measure came for.
Ratio
Value
cash operating margin
0.46
current ratio
3.34
current ratio reported
3.13
deferred revenue growth
-12.39
ebit cagr
-79.24
ebit yoy
-95.3
fcf margin
-18.28
interest cover
0.65
net debt ebitda
16.41
operating margin
0.35
owner earnings margin
-18.28
revenue growth
36.33
revenue growth per share
36.33
roic
0.56
rule of 40
36.68
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about MAMK's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-04-30 (487 days old, weighted average diluted); 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`
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: worst year
growth rests on 3 of 4 inputs; not tagged: sustained growth