BIZTRAC BETA
Other recreational activities

SØRFONDEN SLIPP AS

Org. no. 916598513 Limited company (AS) Oslo Incorporated 1977 Active
Ownership graph ↗
Revenue 2025 NOK 11.9m
Operating profit NOK 2.1m
Equity NOK 12.9m
Incorporated 1977
Employees 6
Share capital NOK 100,000

SØRFONDEN SLIPP AS is registered as a limited company in Oslo, Oslo with organisation number 916598513. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 1977 and has 6 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Drive marina med båtplassutleie, båtopplag, vinterhavn, slippsetting og butikk med båtpuss-rekvisita etc, herunder å delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.9m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 11.9m
Operating profit
NOK 2.1m
Equity
NOK 12.9m
Est. value
NOK 17.1m

Financial health · 2025

Liquidity
4.28
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
89.7%
Very good
Equity as a share of total capital

Who owns SØRFONDEN SLIPP AS?

IVAR SØRFONDEN
SØRFONDEN SLIPP AS
NOK 11.9m rev. · NOK 2.1m profit

SØRFONDEN SLIPP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SØRFONDEN SLIPP AS

Who owns SØRFONDEN SLIPP AS?

IVAR SØRFONDEN is the largest registered owner, with 52.0%.

What is the revenue of SØRFONDEN SLIPP AS?

SØRFONDEN SLIPP AS had revenue of NOK 11.9m in 2025.

Who is the general manager of SØRFONDEN SLIPP AS?

Kristine Sørfonden is registered as general manager of SØRFONDEN SLIPP AS.

Where is SØRFONDEN SLIPP AS based?

SØRFONDEN SLIPP AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.