Every figure this model derived for CTS, 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-03-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
16,263,000
PaymentsToAcquireProductiveAssets
2026-03-31
cash
90,851,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
266,015,000
AssetsCurrent
2026-03-31
current liabilities
105,409,000
LiabilitiesCurrent
2026-03-31
equity
557,475,000
StockholdersEquity
2026-03-31
interest expense
3,850,000
InterestExpenseNonoperating
2026-03-31
ocf
103,882,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
554,780,000
Revenues
2026-03-31
sbc
0
ShareBasedCompensation
2012-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
CTS on one particular measure came for.
Ratio
Value
cash operating margin
22.21
current ratio
2.57
current ratio reported
2.52
deferred revenue growth
3.81
dilution pct
-2.97
ebit cagr
-1.57
ebit yoy
21.12
fcf margin
15.79
growth cv
1.97
interest cover
22.95
operating margin
15.92
owner earnings margin
15.79
revenue growth
7.77
revenue growth per share
11.07
roic
14.96
rule of 40
23.69
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about CTS's figures. Written by the
derivation as it ran, not added afterwards.
no current stock compensation tagged (last tagged 2012-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-04-22 (130 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