Every figure this model derived for TRAK, 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.
The figures themselves rather than their scores — what somebody looking up
TRAK on one particular measure came for.
Ratio
Value
cash operating margin
37.82
current ratio
10.99
current ratio reported
4.89
deferred revenue growth
2.15
dilution pct
1.11
ebit cagr
15.37
ebit yoy
26.61
fcf margin
31.94
growth cv
3.06
interest cover
173.21
operating margin
32.16
owner earnings margin
30.12
revenue growth
6.55
revenue growth per share
5.38
roic
26.15
rule of 40
38.71
sbc pct revenue
1.83
What to be careful about
What this model itself distrusts about TRAK'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 2026-05-14 (108 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.
gross profit not tagged; rebuilt from RevenueFromContractWithCustomerIncludingAssessedTax - CostOfGoodsAndServicesSold
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