Every figure this model derived for DSYWW, 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
capex
518,262
PaymentsToAcquirePropertyPlantAndEquipment
2025-06-30
cash
1,678,970
CashAndCashEquivalentsAtCarryingValue
2025-06-30
current assets
3,839,557
AssetsCurrent
2025-06-30
current liabilities
3,382,259
LiabilitiesCurrent
2025-06-30
equity
173,432
StockholdersEquity
2025-06-30
interest expense
65,692
InterestExpense
2025-06-30
ocf
-6,486,454
NetCashProvidedByUsedInOperatingActivities
2025-06-30
revenue
2,557,266
Revenues
2025-06-30
sbc
34,227,641
ShareBasedCompensation
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
DSYWW on one particular measure came for.
Ratio
Value
cash operating margin
-130.02
current ratio
1.15
current ratio reported
1.14
deferred revenue growth
-98.64
dilution pct
56.47
fcf margin
-273.91
growth cv
2.08
interest cover
-581.7
operating margin
-1494.3
owner earnings margin
-1612.36
revenue growth
-65.08
revenue growth per share
-77.68
rule of 40
-1559.38
What to be careful about
What this model itself distrusts about DSYWW's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: sbc pct revenue -- sbc pct revenue came out at 1,338% against a scale that tops out near 1,250%, which is arithmetic on a revenue figure of 2,557,266 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
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-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`
quality rests on 3 of 5 inputs; not tagged: roic, sbc discipline
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