Every figure this model derived for GTX, 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.
Figure
Value
XBRL tag
As at
capex
75,000,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-03-31
cash
142,000,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
1,375,000,000
AssetsCurrent
2026-03-31
current liabilities
1,406,000,000
LiabilitiesCurrent
2026-03-31
equity
-781,000,000
StockholdersEquity
2026-03-31
interest expense
98,000,000
InterestPaidNet
2026-03-31
ocf
455,000,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
3,691,000,000
Revenues
2026-03-31
sbc
28,000,000
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
GTX on one particular measure came for.
Ratio
Value
cash operating margin
17.31
current ratio
0.99
current ratio reported
0.98
deferred revenue growth
25.0
dilution pct
-9.15
fcf margin
10.3
growth cv
2.58
interest cover
5.19
net debt ebitda
2.09
operating margin
13.79
owner earnings margin
9.54
revenue growth
7.36
revenue growth per share
18.17
roic
81.4
rule of 40
21.15
sbc pct revenue
0.76
What to be careful about
What this model itself distrusts about GTX's figures. Written by the
derivation as it ran, not added afterwards.
presents no operating result; summed as revenue minus the costs it does tag (CostOfGoodsAndServicesSold, SellingGeneralAndAdministrativeExpense). Checked against the company's own figures: the answer lands 2.3% of revenue from the 425M pre-tax profit it reports, which is its interest and other non-operating items
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-04-24 (128 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
growth DROPPED from the total: only 2 of 4 inputs could be computed (margin trend, margin recent 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, growth -- 45% of the model), so this row is not comparable with the others; its total rests on what was left