Every figure this model derived for MIMI, 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.
Figure
Value
XBRL tag
As at
capex
205,054
PaymentsToAcquirePropertyPlantAndEquipment
2026-03-31
cash
964,142
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
2,326,627
AssetsCurrent
2026-03-31
current liabilities
1,232,475
LiabilitiesCurrent
2026-03-31
equity
3,284,813
StockholdersEquity
2026-03-31
interest expense
29,391
InterestExpenseNonoperating
2026-03-31
ocf
-858,394
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
3,050,043
Revenues
2025-03-31
sbc
7,928,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
MIMI on one particular measure came for.
Ratio
Value
cash operating margin
-73.74
current ratio
1.95
current ratio reported
1.89
deferred revenue growth
774.86
dilution pct
15.97
fcf margin
-34.87
interest cover
-351.3
operating margin
-338.52
owner earnings margin
-294.8
revenue growth
-25.28
revenue growth per share
-35.57
roic
-240.85
rpo growth
53879.2
rule of 40
-363.8
sbc pct revenue
259.93
What to be careful about
What this model itself distrusts about MIMI'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 2025-03-31 (517 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: worst year
growth rests on 3 of 4 inputs; not tagged: sustained growth