Every figure this model derived for HOLO, 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
13,985
PaymentsToAcquirePropertyPlantAndEquipment
2025-12-31
cash
390,186,184
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
395,006,431
AssetsCurrent
2025-12-31
current liabilities
11,775,466
LiabilitiesCurrent
2025-12-31
equity
382,818,929
StockholdersEquity
2025-12-31
interest expense
21,740
InterestPaidNet
2025-12-31
ocf
7,891,917
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
56,515,732
Revenues
2025-12-31
sbc
133,754
ShareBasedCompensation
2024-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
HOLO on one particular measure came for.
Ratio
Value
cash operating margin
0.93
current ratio
35.92
current ratio reported
33.54
deferred revenue growth
90.05
dilution pct
4034.55
ebit cagr
-58.57
fcf margin
13.94
growth cv
3.47
interest cover
16.77
operating margin
0.65
owner earnings margin
13.7
revenue growth
38.65
revenue growth per share
-96.65
rule of 40
39.29
sbc pct revenue
0.24
What to be careful about
What this model itself distrusts about HOLO's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
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.
invested capital is -7M (cash exceeds equity plus debt), so return on capital is unbounded rather than undefined; scored as maximal
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