BIZTRAC BETA
Other passenger transport in coastal waters

NORDIC BLU OCEAN AS

Org. no. 923887814 Limited company (AS) Levanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 1.5m
Equity NOK 1.2m
Incorporated 2019
Share capital NOK 30,000

NORDIC BLU OCEAN AS is registered as a limited company in Levanger, Trøndelag with organisation number 923887814. The business is classified under other passenger transport in coastal waters (NACE 50.109). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av båter/skip, samt frakt og passasjer drift og hva herved hører til. Selskapet skal også drive med forvaltning av fast eiendom. Samt kjøp og salg av aksjer og andre verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 1.5m
Equity
NOK 1.2m
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.7%
Satisfactory
Equity as a share of total capital

Who owns NORDIC BLU OCEAN AS?

MORTEN INNHAUG
NORDIC BLU OCEAN AS
NOK 2.2m rev. · NOK 1.5m profit

NORDIC BLU OCEAN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORDIC BLU OCEAN AS own?

NORDIC BLU OCEAN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NORDIC BLU OCEAN AS

Who owns NORDIC BLU OCEAN AS?

MORTEN INNHAUG is the largest registered owner, with 100.0%.

What is the revenue of NORDIC BLU OCEAN AS?

NORDIC BLU OCEAN AS had revenue of NOK 2.2m in 2025.

Where is NORDIC BLU OCEAN AS based?

NORDIC BLU OCEAN AS has its business address in Levanger.

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.