Sasol Limited (SSL)

Every figure this model derived for SSL, 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-06-30.

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	25,345,000,000	`PurchaseOfPropertyPlantAndEquipmentClassifiedAsInvestingActivities`	2025-06-30
cash	41,050,000,000	`CashAndCashEquivalents`	2025-06-30
current assets	177,969,000,000	`CurrentAssets`	2020-06-30
current liabilities	93,118,000,000	`CurrentLiabilities`	2020-06-30
equity	152,427,000,000	`EquityAttributableToOwnersOfParent`	2025-06-30
interest expense	9,462,000,000	`FinanceCosts`	2025-06-30
ocf	38,308,000,000	`CashFlowsFromUsedInOperatingActivities`	2025-06-30
revenue	249,096,000,000	`Revenue`	2025-06-30
sbc	914,000,000	`ExpenseFromSharebasedPaymentTransactionsWithEmployees`	2025-06-30

The ratios

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

Ratio	Value
cash operating margin	13.54
current ratio	1.91
current ratio reported	1.91
dilution pct	1.42
fcf margin	5.2
interest cover	1.99
net debt ebitda	2.45
operating margin	7.55
owner earnings margin	4.84
revenue growth	-9.46
revenue growth per share	-10.73
roic	6.39
rule of 40	-1.9
sbc pct revenue	0.37

What to be careful about

What this model itself distrusts about SSL'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
reports in ZAR and no currency is recorded for its share price, so the two cannot be shown to match. The price refresh records one; until it has run for this company the multiples are left out rather than assumed comparable
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 DROPPED from the total: only 1 of 4 inputs could be computed (sustained growth, margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
3 of 5 dimensions could not be measured (valuation, durability, growth -- 55% of the model), so this row is not comparable with the others; its total rests on what was left