Every figure this model derived for EBZT, 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 2024-10-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.
The figures themselves rather than their scores — what somebody looking up
EBZT on one particular measure came for.
Ratio
Value
cash operating margin
-1375.32
current ratio
0.04
current ratio reported
0.04
deferred revenue growth
0.0
fcf margin
-325.45
growth cv
2.2
interest cover
-70.79
operating margin
-1963.36
owner earnings margin
-767.68
roic
-264.22
sbc pct revenue
442.24
What to be careful about
What this model itself distrusts about EBZT's figures. Written by the
derivation as it ran, not added afterwards.
WITHHELD: net margin -- net margin came out at -5,368% against a scale that tops out near 1,500%, which is arithmetic on a revenue figure of 393,000 rather than a margin. The figure is absent rather than corrected: there is no right value to put here.
newest fact in the filing is 2024-10-31 (1y old); this company's data is not usable and the scores below should be ignored
revenue period ends 2024-10-31 (668 days ago) - the tag chain found nothing recent, so treat this row as unscored
no market cap; set `market_cap` in overrides.yaml
share count is from 2024-10-31 (668 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.
no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
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
growth DROPPED from the total: only 2 of 4 inputs could be computed (revenue growth, sustained growth 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, growth -- 45% of the model), so this row is not comparable with the others; its total rests on what was left