Every figure this model derived for EBON, 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
4,497,134
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
206,361,541
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
216,187,992
AssetsCurrent
2025-12-31
current liabilities
7,914,934
LiabilitiesCurrent
2025-12-31
equity
244,231,820
StockholdersEquity
2025-12-31
ocf
-9,045,139
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
6,536,987
Revenues
2025-12-31
sbc
363,949
AllocatedShareBasedCompensationExpense
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
EBON on one particular measure came for.
Ratio
Value
cash operating margin
-342.38
current ratio
27.51
current ratio reported
27.31
deferred revenue growth
-20.12
dilution pct
0.0
fcf margin
-207.16
growth cv
5.32
operating margin
-387.02
owner earnings margin
-212.73
revenue growth
11.39
revenue growth per share
11.39
roic
-52.78
rule of 40
-375.63
sbc pct revenue
5.57
What to be careful about
What this model itself distrusts about EBON'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, weighted average diluted); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
no debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 206M of net cash against a 14M annual burn is 15.2 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