Every figure this model derived for ETR, 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
8,277,046,000
PaymentsToAcquirePropertyPlantAndEquipment
2026-03-31
cash
3,571,053,000
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
7,810,059,000
AssetsCurrent
2026-03-31
current liabilities
8,159,972,000
LiabilitiesCurrent
2026-03-31
equity
17,346,741,000
StockholdersEquity
2026-03-31
interest expense
1,464,487,000
InterestExpenseDebt
2026-03-31
ocf
5,443,427,000
NetCashProvidedByUsedInOperatingActivities
2026-03-31
revenue
13,287,438,000
Revenues
2026-03-31
sbc
0
AllocatedShareBasedCompensationExpense
2010-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
ETR on one particular measure came for.
Ratio
Value
cash operating margin
40.72
current ratio
0.96
current ratio reported
0.96
deferred revenue growth
6.39
dilution pct
4.31
ebit cagr
13.28
ebit yoy
-1.25
fcf margin
-21.33
growth cv
1.96
interest cover
2.1
net debt ebitda
5.68
operating margin
23.14
owner earnings margin
-21.33
revenue growth
11.36
revenue growth per share
6.76
roic
5.05
rule of 40
34.5
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about ETR's figures. Written by the
derivation as it ran, not added afterwards.
no current stock compensation tagged (last tagged 2010-12-31); treated as zero, so owner earnings are overstated
no market cap; set `market_cap` in overrides.yaml
share count is from 2026-03-31 (152 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`
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
durability rests on 3 of 4 inputs; not tagged: gross margin stability