Paramount Skydance Corporation (PSKY)

Every figure this model derived for PSKY, 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
capex	263,000,000	`PaymentsToAcquirePropertyPlantAndEquipment`	2024-12-31
cash	1,627,000,000	`CashAndCashEquivalentsAtCarryingValue`	2026-06-30
current assets	11,020,000,000	`AssetsCurrent`	2026-06-30
current liabilities	10,600,000,000	`LiabilitiesCurrent`	2026-06-30
equity	11,771,000,000	`StockholdersEquity`	2026-06-30
interest expense	860,000,000	`InterestExpenseNonoperating`	2024-12-31
ocf	752,000,000	`NetCashProvidedByUsedInOperatingActivities`	2024-12-31
revenue	29,213,000,000	`RevenueFromContractWithCustomerExcludingAssessedTax`	2024-12-31
sbc	245,000,000	`ShareBasedCompensation`	2024-12-31

The ratios

The figures themselves rather than their scores — what somebody looking up PSKY on one particular measure came for.

Ratio	Value
cash operating margin	-15.86
current ratio	1.04
current ratio reported	1.04
dilution pct	1.84
fcf margin	1.67
interest cover	-6.13
operating margin	-18.04
owner earnings margin	0.84
revenue growth	-1.48
revenue growth per share	-3.26
roic	-16.45
rule of 40	-19.52
sbc pct revenue	0.84

What to be careful about

What this model itself distrusts about PSKY'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 market cap; set `market_cap` in overrides.yaml
share count is from 2025-11-05 (298 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 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability 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