Every figure this model derived for MALG, 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 2022-09-30.
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
14,211
PaymentsToAcquirePropertyPlantAndEquipment
2022-09-30
cash
3,685,863
CashAndCashEquivalentsAtCarryingValue
2022-09-30
current assets
31,149,632
AssetsCurrent
2022-09-30
current liabilities
1,049,849
LiabilitiesCurrent
2022-09-30
equity
30,549,807
StockholdersEquity
2022-09-30
ocf
2,864,805
NetCashProvidedByUsedInOperatingActivities
2022-09-30
revenue
22,883,710
Revenues
2022-09-30
The ratios
The figures themselves rather than their scores — what somebody looking up
MALG on one particular measure came for.
Ratio
Value
cash operating margin
58.76
current ratio
60.28
current ratio reported
29.67
deferred revenue growth
105.62
dilution pct
0.5
ebit yoy
-31.11
fcf margin
12.46
operating margin
58.03
owner earnings margin
12.46
revenue growth
-21.58
revenue growth per share
-21.97
roic
38.6
rule of 40
36.45
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about MALG's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2022-09-30 (3y old); this company's data is not usable and the scores below should be ignored
revenue period ends 2022-09-30 (1430 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
share count is from 2022-09-30 (1430 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 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
resilience rests on 2 of 3 inputs; not tagged: interest cover
growth rests on 3 of 4 inputs; not tagged: sustained growth
no interest expense tagged while 0M of debt is on the balance sheet, so interest cover is unmeasured rather than perfect