Every figure this model derived for DSP, 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 2026-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
DSP on one particular measure came for.
Ratio
Value
cash operating margin
15.28
current ratio
2.37
current ratio reported
2.34
deferred revenue growth
282.25
dilution pct
227.52
ebit yoy
78.94
fcf margin
17.0
growth cv
0.97
interest cover
32.32
operating margin
2.35
owner earnings margin
9.43
revenue growth
21.99
revenue growth per share
-62.75
rule of 40
24.33
sbc pct revenue
7.56
What to be careful about
What this model itself distrusts about DSP's figures. Written by the
derivation as it ran, not added afterwards.
no market cap; set `market_cap` in overrides.yaml
invested capital is -80M (cash exceeds equity plus debt), so return on capital is unbounded rather than undefined; scored as maximal
gross profit not tagged; rebuilt from RevenueFromContractWithCustomerExcludingAssessedTax - CostOfGoodsAndServicesSold
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