Every figure this model derived for FULO, 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 2023-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
2023-12-31
cash
3,130,331
CashAndCashEquivalentsAtCarryingValue
2023-12-31
current assets
3,166,844
AssetsCurrent
2023-12-31
current liabilities
1,780,592
LiabilitiesCurrent
2023-12-31
equity
1,622,188
StockholdersEquity
2023-12-31
ocf
690,293
NetCashProvidedByUsedInOperatingActivities
2023-12-31
revenue
4,191,084
Revenues
2023-12-31
sbc
8,215
AllocatedShareBasedCompensationExpense
2023-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
FULO on one particular measure came for.
Ratio
Value
cash operating margin
12.81
current ratio
1.78
current ratio reported
1.78
deferred revenue growth
6.14
dilution pct
3.95
ebit cagr
26.42
ebit yoy
-38.3
fcf margin
16.47
growth cv
1.0
operating margin
12.22
owner earnings margin
16.27
revenue growth
-1.81
revenue growth per share
-5.54
rule of 40
10.41
sbc pct revenue
0.2
What to be careful about
What this model itself distrusts about FULO's figures. Written by the
derivation as it ran, not added afterwards.
newest fact in the filing is 2024-02-15 (2y old); this company's data is not usable and the scores below should be ignored
revenue is annual, not TTM
revenue period ends 2023-12-31 (973 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 2023-12-31 (973 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.
invested capital is -2M (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
durability rests on 3 of 4 inputs; not tagged: contracted coverage