Every figure this model derived for WULF, 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-06-30.
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
2,225,074,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-06-30
cash
2,619,191,000
CashAndCashEquivalentsAtCarryingValue
2026-06-30
current assets
2,806,504,000
AssetsCurrent
2026-06-30
current liabilities
3,763,871,000
LiabilitiesCurrent
2026-06-30
equity
147,284,000
StockholdersEquity
2026-06-30
interest expense
195,647,000
InterestExpenseNonoperating
2026-06-30
ocf
-279,157,000
NetCashProvidedByUsedInOperatingActivities
2026-06-30
revenue
165,193,000
Revenues
2026-06-30
sbc
196,288,000
ShareBasedCompensation
2026-06-30
The ratios
The figures themselves rather than their scores — what somebody looking up
WULF on one particular measure came for.
Ratio
Value
cash operating margin
-68.61
current ratio
0.75
current ratio reported
0.75
dilution pct
13.19
fcf margin
-1515.94
growth cv
1.48
interest cover
-2.11
operating margin
-250.37
owner earnings margin
-1634.77
revenue growth
14.65
revenue growth per share
1.29
roic
-48.35
rule of 40
-235.72
sbc pct revenue
118.82
What to be careful about
What this model itself distrusts about WULF's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: capex intensity -- capex intensity came out at 1,347% against a scale that tops out near 1,250%, which is arithmetic on a revenue figure of 165,193,000 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
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`
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