BIZTRAC BETA
Construction of utility projects for electricity and telecommunications at sea

FRED. OLSEN OCEAN AS

Org. no. 970897356 Limited company (AS) Oslo Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 20.4m
Operating profit NOK 1.0m
Equity NOK 14.0m
Incorporated 1994
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FRED. OLSEN OCEAN AS is registered as a limited company in Oslo, Oslo with organisation number 970897356. The business is classified under construction of utility projects for electricity and telecommunications at sea (NACE 42.221). The company was incorporated in 1994. Registered share capital is NOK 500,000. The company's stated purpose is: “Yte rådgivende tjenester, informasjonsvirksomhet og regnskapsførsel for selskap relatert til skips- fart og investeringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 20.4m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 20.4m
Operating profit
NOK 1.0m
Equity
NOK 14.0m
Est. value
NOK 9.9m

Financial health · 2024

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

Who owns FRED. OLSEN OCEAN AS?

FRED. OLSEN OCEAN LTD.
FRED. OLSEN OCEAN AS
NOK 20.4m rev. · NOK 1.0m profit

FRED. OLSEN OCEAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRED. OLSEN OCEAN AS

Who owns FRED. OLSEN OCEAN AS?

FRED. OLSEN OCEAN LTD. is the largest registered owner, with 100.0%.

What is the revenue of FRED. OLSEN OCEAN AS?

FRED. OLSEN OCEAN AS had revenue of NOK 20.4m in 2024.

Where is FRED. OLSEN OCEAN AS based?

FRED. OLSEN OCEAN 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.