Every figure this model derived for ITRN, 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
21,776,000
PaymentsToAcquireProductiveAssets
2025-12-31
cash
107,554,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
237,644,000
AssetsCurrent
2025-12-31
current liabilities
104,105,000
LiabilitiesCurrent
2025-12-31
equity
217,564,000
StockholdersEquity
2025-12-31
interest expense
0
InterestPaidNet
2025-12-31
ocf
88,578,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
359,023,000
Revenues
2025-12-31
sbc
0
AllocatedShareBasedCompensationExpense
2018-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
ITRN on one particular measure came for.
Ratio
Value
cash operating margin
25.3
current ratio
3.09
current ratio reported
2.28
deferred revenue growth
19.03
dilution pct
-0.1
ebit cagr
8.98
ebit yoy
8.23
fcf margin
18.61
growth cv
0.23
operating margin
21.45
owner earnings margin
18.61
revenue growth
6.77
revenue growth per share
6.88
roic
55.32
rule of 40
28.23
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about ITRN'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 (last tagged 2018-06-30); 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