Every figure this model derived for MOMO, 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.
The figures themselves rather than their scores — what somebody looking up
MOMO on one particular measure came for.
Ratio
Value
cash operating margin
15.05
current ratio
6.04
current ratio reported
4.68
deferred revenue growth
14.27
dilution pct
-9.37
ebit yoy
-7.76
fcf margin
6.66
interest cover
18.7
operating margin
13.07
owner earnings margin
5.09
revenue growth
2.44
revenue growth per share
13.04
roic
18.96
rule of 40
15.51
sbc pct revenue
1.57
What to be careful about
What this model itself distrusts about MOMO's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
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.
gross profit not tagged; rebuilt from RevenueFromContractWithCustomerExcludingAssessedTax - CostOfRevenue
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