Every figure this model derived for HTHT, 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
0
PaymentsToAcquirePropertyPlantAndEquipment
2012-12-31
cash
2,185,000,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
2,493,000,000
AssetsCurrent
2025-12-31
current liabilities
2,735,000,000
LiabilitiesCurrent
2025-12-31
equity
1,831,000,000
StockholdersEquity
2025-12-31
interest expense
48,000,000
InterestExpenseNonoperating
2025-12-31
ocf
1,198,000,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
3,618,000,000
Revenues
2025-12-31
sbc
60,000,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
HTHT on one particular measure came for.
Ratio
Value
cash operating margin
33.58
current ratio
1.01
current ratio reported
0.91
deferred revenue growth
4.4
dilution pct
-0.94
ebit cagr
147.46
ebit yoy
36.75
fcf margin
33.11
growth cv
0.98
interest cover
20.31
operating margin
26.95
owner earnings margin
31.45
revenue growth
10.51
revenue growth per share
11.56
roic
481.41
rule of 40
37.46
sbc pct revenue
1.66
What to be careful about
What this model itself distrusts about HTHT'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 capital expenditure tagged (last tagged 2012-12-31); treated as zero, so free cash flow is overstated and equals operating cash flow
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
durability rests on 3 of 4 inputs; not tagged: gross margin stability