Every figure this model derived for DSX-WT, 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.
Figure
Value
XBRL tag
As at
capex
1,671,000
PaymentsToAcquireOtherPropertyPlantAndEquipment
2025-12-31
cash
48,678,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
276,585,000
AssetsCurrent
2026-06-30
current liabilities
135,136,000
LiabilitiesCurrent
2026-06-30
equity
551,452,000
StockholdersEquity
2026-06-30
interest expense
42,951,000
InterestExpense
2025-12-31
ocf
47,507,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
213,541,000
Revenues
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
DSX-WT on one particular measure came for.
Ratio
Value
cash operating margin
41.54
current ratio
2.12
current ratio reported
2.05
deferred revenue growth
14.78
dilution pct
-6.88
ebit cagr
-9.72
ebit yoy
-28.22
fcf margin
21.46
growth cv
3.09
interest cover
0.98
net debt ebitda
7.28
operating margin
19.76
owner earnings margin
21.46
revenue growth
-6.43
revenue growth per share
0.49
roic
2.78
rule of 40
13.33
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about DSX-WT'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 stock compensation tagged; treated as zero, so owner earnings are overstated
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 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: gross margin stability