Every figure this model derived for TRI, 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.
The figures themselves rather than their scores — what somebody looking up
TRI on one particular measure came for.
Ratio
Value
cash operating margin
31.49
current ratio
0.64
current ratio reported
0.64
dilution pct
-0.38
ebit cagr
14.46
ebit yoy
1.09
fcf margin
26.98
growth cv
0.37
interest cover
15.45
net debt ebitda
1.14
operating margin
28.52
owner earnings margin
25.49
revenue growth
3.0
revenue growth per share
3.39
roic
11.63
rule of 40
31.52
sbc pct revenue
1.48
What to be careful about
What this model itself distrusts about TRI's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income 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
durability DROPPED from the total: only 2 of 4 inputs could be computed (contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left