ESS Tech, Inc. (GWH)

Every figure this model derived for GWH, 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	3,328,000	`PaymentsToAcquirePropertyPlantAndEquipment`	2026-06-30
cash	10,848,000	`CashAndCashEquivalentsAtCarryingValue`	2026-06-30
current assets	13,590,000	`AssetsCurrent`	2026-06-30
current liabilities	20,000,000	`LiabilitiesCurrent`	2026-06-30
equity	-2,687,000	`StockholdersEquity`	2026-06-30
interest expense	520,000	`InterestPaidNet`	2025-12-31
ocf	-42,089,000	`NetCashProvidedByUsedInOperatingActivities`	2026-06-30
revenue	1,583,000	`RevenueFromContractWithCustomerExcludingAssessedTax`	2025-12-31
sbc	4,480,000	`ShareBasedCompensation`	2026-06-30

The ratios

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

Ratio	Value
current ratio	0.69
current ratio reported	0.68
deferred revenue growth	-79.75
dilution pct	24.04
growth cv	1.71
interest cover	-108.88
revenue growth	-74.85
revenue growth per share	-79.73
roic	-4733.14
rule of 40	-3651.48
sbc pct revenue	283.01

What to be careful about

What this model itself distrusts about GWH'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 -- net margin came out at -4,159% against a scale that tops out near 1,500%, which is arithmetic on a revenue figure of 1,583,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
no market cap; set `market_cap` in overrides.yaml
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 2 of 5 inputs could be computed (operating margin, 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
growth DROPPED from the total: only 2 of 4 inputs could be computed (sustained growth, margin trend not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (quality, valuation, growth -- 75% of the model), so this row is not comparable with the others; its total rests on what was left