Every figure this model derived for PONY, 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
PONY on one particular measure came for.
Ratio
Value
cash operating margin
-247.73
current ratio
13.96
current ratio reported
13.67
deferred revenue growth
-40.66
dilution pct
232.6
fcf margin
-232.03
growth cv
0.73
operating margin
-289.84
owner earnings margin
-266.25
revenue growth
19.96
revenue growth per share
-63.93
roic
-41.12
rule of 40
-269.88
sbc pct revenue
34.22
What to be careful about
What this model itself distrusts about PONY'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, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
no debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 1,151M of net cash against a 209M annual burn is 5.5 years
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
growth rests on 3 of 4 inputs; not tagged: sustained growth
no interest expense tagged while 15M of debt is on the balance sheet, so interest cover is unmeasured rather than perfect