Every figure this model derived for TRANS.ST, 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 2024-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
cash
126,061,000
CashAndCashEquivalents
2025-01-01
equity
556,471,000
EquityAttributableToOwnersOfParent
2025-01-01
interest expense
77,859,000
FinanceCosts
2024-12-31
ocf
185,559,000
CashFlowsFromUsedInOperatingActivities
2024-12-31
revenue
2,488,722,000
Revenue
2024-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
TRANS.ST on one particular measure came for.
Ratio
Value
cash operating margin
1.61
fcf margin
7.46
interest cover
0.51
net debt ebitda
2.51
operating margin
1.61
owner earnings margin
7.46
revenue growth
-7.44
revenue growth per share
-7.44
roic
4.82
rule of 40
-5.83
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about TRANS.ST's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2025-01-01 (1y old); this company's data is not usable and the scores below should be ignored
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2024-12-31 (610 days ago) - the tag chain found nothing recent, so treat this row as unscored
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no current capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
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 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
resilience rests on 2 of 3 inputs; not tagged: liquidity
growth DROPPED from the total: only 1 of 4 inputs could be computed (sustained growth, margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (valuation, durability, growth -- 55% of the model), so this row is not comparable with the others; its total rests on what was left