Every figure this model derived for MLGO, 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-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.
Figure
Value
XBRL tag
As at
capex
1,159
PaymentsToAcquireProductiveAssets
2025-12-31
cash
336,767,914
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
350,147,879
AssetsCurrent
2025-12-31
current liabilities
15,542,115
LiabilitiesCurrent
2025-12-31
equity
330,326,540
StockholdersEquity
2025-12-31
interest expense
108,045
InterestPaidNet
2025-12-31
ocf
2,481,467
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
60,045,146
Revenues
2025-12-31
sbc
0
ShareBasedCompensation
2023-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
MLGO on one particular measure came for.
Ratio
Value
cash operating margin
5.63
current ratio
24.1
current ratio reported
22.53
deferred revenue growth
113.59
dilution pct
-20.76
ebit cagr
-20.7
ebit yoy
13.65
fcf margin
4.13
interest cover
29.47
operating margin
5.3
owner earnings margin
4.13
revenue growth
-20.29
revenue growth per share
0.59
rule of 40
-14.99
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about MLGO'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 (last tagged 2023-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 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.
invested capital is -6M (cash exceeds equity plus debt), so return on capital is unbounded rather than undefined; scored as maximal
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