Every figure this model derived for SFL, 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
0
PaymentsToAcquireOtherProductiveAssets
2022-12-31
cash
150,829,000
CashAndCashEquivalentsAtCarryingValue
2025-12-31
current assets
259,218,000
AssetsCurrent
2025-12-31
current liabilities
710,325,000
LiabilitiesCurrent
2025-12-31
equity
960,862,000
StockholdersEquity
2025-12-31
interest expense
180,527,000
InterestExpenseNonoperating
2025-12-31
ocf
267,143,000
NetCashProvidedByUsedInOperatingActivities
2025-12-31
revenue
733,041,000
Revenues
2025-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
SFL on one particular measure came for.
Ratio
Value
cash operating margin
50.7
current ratio
0.36
current ratio reported
0.36
deferred revenue growth
-100.0
dilution pct
2.36
ebit cagr
-13.38
ebit yoy
-55.44
fcf margin
36.44
growth cv
1.56
interest cover
0.76
net debt ebitda
7.23
operating margin
18.65
owner earnings margin
36.44
revenue growth
-18.95
revenue growth per share
-20.82
roic
2.96
rule of 40
-0.3
sbc pct revenue
0.0
What to be careful about
What this model itself distrusts about SFL'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 current capital expenditure tagged (last tagged 2022-12-31); treated as zero, so free cash flow is overstated and equals operating cash flow
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.
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 DROPPED from the total: only 2 of 4 inputs could be computed (contracted coverage, gross margin stability 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, durability -- 35% of the model), so this row is not comparable with the others; its total rests on what was left