Every figure this model derived for EFTY, 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
687,059
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
5,426,805
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
5,977,589
AssetsCurrent
2025-12-31
current liabilities
1,368,474
LiabilitiesCurrent
2025-12-31
equity
5,797,012
StockholdersEquity
2025-12-31
interest expense
50,516
InterestExpenseNonoperating
2025-12-31
ocf
-910,681
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
3,222,344
Revenues
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
EFTY on one particular measure came for.
Ratio
Value
cash operating margin
3.34
current ratio
6.15
current ratio reported
4.37
deferred revenue growth
-58.58
dilution pct
3.39
fcf margin
-49.58
interest cover
-0.63
operating margin
-0.99
owner earnings margin
-49.58
revenue growth
27.57
revenue growth per share
23.39
roic
-6.81
rpo growth
-60.33
rule of 40
26.58
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about EFTY'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 market cap; set `market_cap` in overrides.yaml
share count is from 2025-12-31 (242 days old, weighted average diluted); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
gross profit not tagged; rebuilt from Revenues - OperatingCostsAndExpenses
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: worst year
growth rests on 3 of 4 inputs; not tagged: sustained growth