Every figure this model derived for STFS, 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-06-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
cash
14,816,331
CashAndCashEquivalentsAtCarryingValue
2025-06-30
current assets
87,342,584
AssetsCurrent
2025-06-30
current liabilities
41,421,562
LiabilitiesCurrent
2025-06-30
equity
45,921,022
StockholdersEquity
2025-06-30
interest expense
206,296
InterestExpenseDebt
2025-06-30
ocf
-28,401,519
NetCashProvidedByUsedInOperatingActivities
2025-06-30
revenue
120,789,049
Revenues
2025-06-30
sbc
119,596,950
ShareBasedCompensation
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
STFS on one particular measure came for.
Ratio
Value
cash operating margin
-8.38
current ratio
2.24
current ratio reported
2.11
deferred revenue growth
12.45
dilution pct
0.0
fcf margin
-23.51
interest cover
-628.81
operating margin
-107.39
owner earnings margin
-122.53
revenue growth
11.01
revenue growth per share
11.01
roic
-329.47
rule of 40
-96.38
sbc pct revenue
99.01
What to be careful about
What this model itself distrusts about STFS'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 capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
reports in CNY and no currency is recorded for its share price, so the two cannot be shown to match. The price refresh records one; until it has run for this company the multiples are left out rather than assumed comparable
share count is from 2025-06-30 (426 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 DROPPED from the total: only 1 of 4 inputs could be computed (worst year, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth DROPPED from the total: only 2 of 4 inputs could be computed (sustained growth, margin trend not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (valuation, durability, growth -- 55% of the model), so this row is not comparable with the others; its total rests on what was left