Every figure this model derived for WIMI, 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
8,358,080
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
480,422,733
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
501,200,211
AssetsCurrent
2025-12-31
current liabilities
131,034,573
LiabilitiesCurrent
2025-12-31
equity
314,265,649
StockholdersEquity
2025-12-31
interest expense
108,045
InterestPaidNet
2025-12-31
ocf
16,749,993
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
60,073,613
Revenues
2025-12-31
sbc
3,138,941
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
WIMI on one particular measure came for.
Ratio
Value
cash operating margin
-2.74
current ratio
3.86
current ratio reported
3.82
deferred revenue growth
105.34
fcf margin
13.97
interest cover
-50.89
operating margin
-9.15
owner earnings margin
8.74
revenue growth
-20.31
revenue growth per share
-20.31
rule of 40
-29.47
sbc pct revenue
5.23
What to be careful about
What this model itself distrusts about WIMI'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.
diluted share count moved +98% in a year (10M to 19M, a ratio of 1.98), which is a stock split rather than issuance; growth is measured on total revenue, not per share
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`
quality rests on 4 of 5 inputs; not tagged: roic
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