Every figure this model derived for BHST, 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
2,355,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
23,025,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
30,500,000
AssetsCurrent
2025-12-31
current liabilities
7,684,000
LiabilitiesCurrent
2025-12-31
equity
25,448,000
StockholdersEquity
2025-12-31
interest expense
0
InterestPaid
2024-12-31
ocf
-7,226,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
34,508,000
Revenues
2025-12-31
sbc
601,000
AllocatedShareBasedCompensationExpense
2024-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
BHST on one particular measure came for.
Ratio
Value
cash operating margin
-9.71
current ratio
3.97
current ratio reported
3.97
fcf margin
-27.76
operating margin
-16.16
owner earnings margin
-29.51
revenue growth
37.0
revenue growth per share
37.0
roic
-35.09
rule of 40
20.85
sbc pct revenue
1.74
What to be careful about
What this model itself distrusts about BHST's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
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 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 debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 13M of net cash against a 10M annual burn is 1.3 years
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 2 of 4 inputs could be computed (worst year, contracted coverage not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth rests on 3 of 4 inputs; not tagged: sustained growth
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left