Every figure this model derived for EHGO, 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
137,533
PaymentsToAcquirePropertyPlantAndEquipment
2026-03-31
cash
5,089,321
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
19,559,055
AssetsCurrent
2026-03-31
current liabilities
6,055,139
LiabilitiesCurrent
2026-03-31
equity
8,833,834
StockholdersEquity
2026-03-31
interest expense
125,972
InterestExpenseNonoperating
2026-03-31
ocf
-5,675,011
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
16,318,923
Revenues
2026-03-31
sbc
1,493,208
ShareBasedCompensation
2026-03-31
The ratios
The figures themselves rather than their scores — what somebody looking up
EHGO on one particular measure came for.
Ratio
Value
cash operating margin
-62.65
current ratio
4.05
current ratio reported
3.23
deferred revenue growth
23.11
fcf margin
-35.62
interest cover
-95.18
operating margin
-73.47
owner earnings margin
-44.77
revenue growth
21.13
revenue growth per share
21.13
roic
-251.5
rule of 40
-52.34
sbc pct revenue
9.15
What to be careful about
What this model itself distrusts about EHGO'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 2026-03-31 (152 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.
diluted share count moved +52% in a year (1M to 2M, a ratio of 1.52), which is a stock split rather than issuance; growth is measured on total revenue, not per share
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