HIGHWAY HOLDINGS LIMITED (HIHO)

Every figure this model derived for HIHO, 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 2026-03-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	103,000	`PaymentsToAcquirePropertyPlantAndEquipment`	2026-03-31
cash	5,476,000	`CashAndCashEquivalentsAtCarryingValue`	2026-03-31
current assets	7,137,000	`AssetsCurrent`	2026-03-31
current liabilities	3,195,000	`LiabilitiesCurrent`	2026-03-31
equity	4,892,000	`StockholdersEquity`	2026-03-31
interest expense	1,000	`InterestExpenseDebt`	2026-03-31
ocf	-1,411,000	`NetCashProvidedByUsedInOperatingActivities`	2026-03-31
revenue	57,000	`RevenueFromContractWithCustomerExcludingAssessedTax`	2026-03-31
sbc	121,000	`AllocatedShareBasedCompensationExpense`	2026-03-31

The ratios

The figures themselves rather than their scores — what somebody looking up HIHO on one particular measure came for.

Ratio	Value
current ratio	2.23
current ratio reported	2.23
dilution pct	3.47
interest cover	-2307.0
sbc pct revenue	212.28

What to be careful about

What this model itself distrusts about HIHO's figures. Written by the derivation as it ran, not added afterwards.

WITHHELD: operating margin, cash operating margin, owner earnings margin, fcf margin, net margin, ocf margin, ebitda margin -- operating margin came out at -4,047% against a scale that tops out near 2,500%, which is arithmetic on a revenue figure of 57,000 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 2026-03-31 (152 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`
quality DROPPED from the total: only 1 of 5 inputs could be computed (operating margin, roic, owner earnings, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
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: revenue growth
2 of 5 dimensions could not be measured (quality, valuation -- 55% of the model), so this row is not comparable with the others; its total rests on what was left