Every figure this model derived for HKIT, 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
2023-12-31
cash
21,656,167
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
40,792,426
AssetsCurrent
2025-12-31
current liabilities
4,954,667
LiabilitiesCurrent
2025-12-31
equity
36,010,312
StockholdersEquity
2025-12-31
interest expense
308,870
InterestExpenseDebt
2025-12-31
ocf
-1,535,849
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
6,536,184
Revenues
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
HKIT on one particular measure came for.
Ratio
Value
cash operating margin
-22.91
current ratio
8.36
current ratio reported
8.23
deferred revenue growth
31.12
dilution pct
2.06
fcf margin
-23.5
growth cv
4.13
interest cover
-5.8
operating margin
-27.41
owner earnings margin
-23.5
revenue growth
125.0
revenue growth per share
120.46
roic
-9.86
rule of 40
97.59
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about HKIT'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 stock compensation tagged; treated as zero, so owner earnings are overstated
no current capital expenditure tagged (last tagged 2023-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, weighted average diluted); 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