Every figure this model derived for TRNS, 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-28.
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
14,682,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-27
cash
6,709,000
CashAndCashEquivalentsAtCarryingValue
2026-06-27
current assets
95,734,000
AssetsCurrent
2026-06-27
current liabilities
38,417,000
LiabilitiesCurrent
2026-06-27
equity
302,899,000
StockholdersEquity
2026-06-27
interest expense
5,669,000
InterestExpenseNonoperating
2026-06-27
ocf
40,044,000
NetCashProvidedByUsedInOperatingActivities
2026-06-27
revenue
331,877,000
Revenues
2026-03-28
sbc
8,397,000
ShareBasedCompensation
2026-06-27
The ratios
The figures themselves rather than their scores — what somebody looking up
TRNS on one particular measure came for.
Ratio
Value
cash operating margin
14.33
current ratio
2.49
current ratio reported
2.49
dilution pct
1.37
ebit cagr
-4.74
ebit yoy
-35.71
fcf margin
7.64
growth cv
0.31
interest cover
2.05
net debt ebitda
2.65
operating margin
3.51
owner earnings margin
5.11
revenue growth
19.2
revenue growth per share
17.59
roic
2.26
rule of 40
22.71
sbc pct revenue
2.53
What to be careful about
What this model itself distrusts about TRNS's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
no market cap; set `market_cap` in overrides.yaml
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