Every figure this model derived for HTT, 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
16,675,893
PaymentsToAcquireProductiveAssets
2025-12-31
cash
916,846,664
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
1,629,065,513
AssetsCurrent
2025-12-31
current liabilities
283,229,445
LiabilitiesCurrent
2025-12-31
equity
1,663,297,234
StockholdersEquity
2025-12-31
interest expense
4,608,405
InterestPaidNet
2025-12-31
ocf
98,248,018
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
5,857,721
Revenues
2025-12-31
sbc
0
AllocatedShareBasedCompensationExpense
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
HTT on one particular measure came for.
Ratio
Value
cash operating margin
-848.81
current ratio
5.75
current ratio reported
5.75
fcf margin
1392.56
interest cover
-12.36
operating margin
-972.58
owner earnings margin
1392.56
revenue growth
-80.24
revenue growth per share
-80.24
roic
-6.03
rpo growth
-100.0
rule of 40
-1052.82
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about HTT's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: net margin -- net margin came out at 1,730% against a scale that tops out near 1,500%, which is arithmetic on a revenue figure of 5,857,721 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
revenue is annual, not TTM
operating income is annual, not TTM
no market cap; set `market_cap` in overrides.yaml
share count is from 2016-12-31 (3529 days old, weighted average diluted); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
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
gross profit not tagged; rebuilt from Revenues - 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
durability rests on 3 of 4 inputs; not tagged: contracted coverage