Every figure this model derived for NCL, 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-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
cash
239,641
CashAndCashEquivalentsAtCarryingValue
2026-03-31
current assets
12,554,381
AssetsCurrent
2026-03-31
current liabilities
8,337,589
LiabilitiesCurrent
2026-03-31
equity
18,449,922
StockholdersEquity
2026-03-31
interest expense
470,900
InterestExpenseNonoperating
2024-12-31
ocf
-1,233,491
NetCashProvidedByUsedInOperatingActivities
2024-12-31
revenue
15,349,854
Revenues
2024-12-31
sbc
2,042,105
ShareBasedCompensation
2024-12-31
The ratios
The figures themselves rather than their scores — what somebody looking up
NCL on one particular measure came for.
Ratio
Value
cash operating margin
6.6
current ratio
1.51
current ratio reported
1.51
dilution pct
29.47
fcf margin
-8.04
interest cover
-3.55
operating margin
-10.91
owner earnings margin
-21.34
revenue growth
9.86
revenue growth per share
-15.14
roic
-7.0
rule of 40
-1.04
sbc pct revenue
13.3
What to be careful about
What this model itself distrusts about NCL's figures. Written by the
derivation as it ran, not added afterwards.
revenue is annual, not TTM
operating income is annual, not TTM
revenue period ends 2024-12-31 (607 days ago) - the tag chain found nothing recent, so treat this row as unscored
no current capital expenditure tagged; 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 2026-03-31 (152 days old, balance sheet); 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 (worst year, contracted coverage not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
growth rests on 3 of 4 inputs; not tagged: sustained growth
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