Every figure this model derived for ECO, 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
cash
116,636,741
CashAndCashEquivalents
2025-12-31
current assets
234,944,340
CurrentAssets
2025-12-31
current liabilities
156,907,893
CurrentLiabilities
2025-12-31
equity
573,091,238
Equity
2025-12-31
interest expense
42,153,588
InterestExpense
2025-12-31
ocf
111,301,518
CashFlowsFromUsedInOperatingActivities
2025-12-31
revenue
391,548,819
Revenue
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
ECO on one particular measure came for.
Ratio
Value
cash operating margin
52.09
current ratio
1.5
current ratio reported
1.5
dilution pct
1.19
ebit cagr
50.09
ebit yoy
-0.25
fcf margin
28.43
growth cv
1.1
interest cover
3.86
net debt ebitda
2.4
operating margin
41.51
owner earnings margin
28.43
revenue growth
-0.43
revenue growth per share
-1.59
roic
12.09
rule of 40
41.08
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about ECO's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
no current stock compensation tagged; treated as zero, so owner earnings are overstated
no current capital expenditure tagged; treated as zero, so free cash flow is overstated and equals operating cash flow
no market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 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 DROPPED from the total: only 2 of 4 inputs could be computed (contracted coverage, gross margin stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
2 of 5 dimensions could not be measured (valuation, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left