Every figure this model derived for ESEA, 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
0
PaymentsToAcquirePropertyPlantAndEquipment
2020-12-31
cash
176,460,053
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
192,351,089
AssetsCurrent
2025-12-31
current liabilities
39,352,279
LiabilitiesCurrent
2025-12-31
equity
463,443,787
StockholdersEquity
2025-12-31
interest expense
14,518,405
InterestExpense
2025-12-31
ocf
141,133,485
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
227,873,562
Revenues
2025-12-31
sbc
1,959,564
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
ESEA on one particular measure came for.
Ratio
Value
cash operating margin
79.02
current ratio
5.65
current ratio reported
4.89
deferred revenue growth
-35.76
dilution pct
-0.2
ebit cagr
34.46
ebit yoy
24.57
fcf margin
61.93
growth cv
1.0
interest cover
10.3
net debt ebitda
0.23
operating margin
65.61
owner earnings margin
61.08
revenue growth
7.03
revenue growth per share
7.25
roic
23.44
rule of 40
72.64
sbc pct revenue
0.86
What to be careful about
What this model itself distrusts about ESEA'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 capital expenditure tagged (last tagged 2020-12-31); 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 rests on 3 of 4 inputs; not tagged: gross margin stability