Every figure this model derived for SSYS, 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
22,113,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
244,527,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
581,984,000
AssetsCurrent
2025-12-31
current liabilities
163,041,000
LiabilitiesCurrent
2025-12-31
equity
842,900,000
StockholdersEquity
2025-12-31
ocf
15,144,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
551,102,000
Revenues
2025-12-31
sbc
24,274,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
SSYS on one particular measure came for.
Ratio
Value
cash operating margin
-0.91
current ratio
5.05
current ratio reported
3.57
deferred revenue growth
3.21
dilution pct
15.17
fcf margin
-1.26
growth cv
5.96
operating margin
-13.15
owner earnings margin
-5.67
revenue growth
-3.73
revenue growth per share
-16.41
roic
-9.57
rule of 40
-16.88
sbc pct revenue
4.4
What to be careful about
What this model itself distrusts about SSYS'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-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: 245M of net cash against a 7M annual burn is 35.1 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