Every figure this model derived for JFU, 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
381,000
PaymentsToAcquireProductiveAssets
2025-12-31
cash
63,193,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
equity
530,789,000
StockholdersEquity
2025-12-31
ocf
29,697,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
19,206,000
Revenues
2025-12-31
sbc
8,000
ShareBasedCompensation
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
JFU on one particular measure came for.
Ratio
Value
cash operating margin
18.48
dilution pct
0.01
fcf margin
152.64
operating margin
8.39
owner earnings margin
152.6
revenue growth
12.18
revenue growth per share
12.17
roic
0.27
rule of 40
20.57
sbc pct revenue
0.04
What to be careful about
What this model itself distrusts about JFU'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, weighted average diluted); 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: contracted coverage
resilience rests on 2 of 3 inputs; not tagged: liquidity