Every figure this model derived for HYSR, 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
17,000
PaymentsToAcquirePropertyPlantAndEquipment
2025-06-30
cash
32,878,358
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
33,778,472
AssetsCurrent
2026-03-31
current liabilities
759,514
LiabilitiesCurrent
2024-06-30
equity
32,947,096
StockholdersEquity
2026-03-31
interest expense
626
InterestExpenseNonoperating
2025-06-30
ocf
-4,528,448
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
1,250
Revenues
2026-03-31
sbc
902,676
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
HYSR on one particular measure came for.
Ratio
Value
current ratio
44.47
current ratio reported
44.47
dilution pct
5.79
interest cover
-10710.96
What to be careful about
What this model itself distrusts about HYSR's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: operating margin, cash operating margin, sbc pct revenue, owner earnings margin, fcf margin, net margin, capex intensity, ocf margin, ebitda margin -- operating margin came out at -536,405% against a scale that tops out near 2,500%, which is arithmetic on a revenue figure of 1,250 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
only 273 days of filings, not a full year: margins and growth are measured, but return on capital and every enterprise-value multiple are refused rather than annualised
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-05-08 (114 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 0 of 5 inputs could be computed (operating margin, roic, sbc discipline, 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 ebit, 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 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth DROPPED from the total: only 1 of 4 inputs could be computed (revenue growth, sustained growth, margin trend not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
4 of 5 dimensions could not be measured (quality, valuation, durability, growth -- 85% of the model), so this row is not comparable with the others; its total rests on what was left