Every figure this model derived for HPAI, 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-06-30.
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
152,051
CashAndCashEquivalentsAtCarryingValue
2025-06-30
current assets
23,766,378
AssetsCurrent
2025-06-30
current liabilities
19,091,103
LiabilitiesCurrent
2025-06-30
equity
17,465,371
StockholdersEquity
2025-06-30
interest expense
16,742
InterestExpenseDebt
2025-06-30
ocf
9,067,013
NetCashProvidedByUsedInOperatingActivities
2025-06-30
revenue
34,856,807
Revenues
2025-06-30
sbc
584,150
ShareBasedCompensation
2025-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
HPAI on one particular measure came for.
Ratio
Value
cash operating margin
9.56
current ratio
1.24
current ratio reported
1.24
dilution pct
23.63
ebit cagr
40.96
ebit yoy
-70.12
fcf margin
26.01
growth cv
0.85
interest cover
164.12
net debt ebitda
0.54
operating margin
7.88
owner earnings margin
24.34
revenue growth
17.86
revenue growth per share
-4.67
roic
11.46
rule of 40
25.74
sbc pct revenue
1.68
What to be careful about
What this model itself distrusts about HPAI'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; 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-06-30 (426 days old, balance sheet); 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: contracted coverage
growth rests on 3 of 4 inputs; not tagged: sustained growth