Every figure this model derived for VSTD, 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.
The figures themselves rather than their scores — what somebody looking up
VSTD on one particular measure came for.
Ratio
Value
cash operating margin
-19.92
current ratio
0.57
current ratio reported
0.57
dilution pct
1.26
fcf margin
-15.26
growth cv
0.45
interest cover
-5.97
operating margin
-27.42
owner earnings margin
-15.92
revenue growth
30.39
revenue growth per share
28.77
roic
-41.39
rule of 40
2.97
sbc pct revenue
0.66
What to be careful about
What this model itself distrusts about VSTD's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-06-30 (426 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 - CostOfServicesCatering
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: contracted coverage
growth rests on 3 of 4 inputs; not tagged: sustained growth