BIZTRAC BETA
Other technical consultancy

OCEANFRONT AS

Org. no. 917082669 Limited company (AS) Kristiansund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 6.4m
Operating profit NOK −1.5m
Equity NOK −4.1m
Incorporated 2016
Share capital NOK 1.1m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).

OCEANFRONT AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 917082669. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2016. Registered share capital is NOK 1.1m, divided into 58825 shares. The company's stated purpose is: “Maritime operasjoner og undervannsvirksomhet, samt øvrig virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.4m in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 6.4m
Operating profit
NOK −1.5m
Equity
NOK −4.1m

Financial health · 2024

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-67.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OCEANFRONT AS?

ESEA GROUP AS
OCEANFRONT AS
NOK 6.4m rev. · NOK −1.5m profit

OCEANFRONT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OCEANFRONT AS own?

OCEANFRONT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OCEANFRONT AS

Who owns OCEANFRONT AS?

ESEA GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of OCEANFRONT AS?

OCEANFRONT AS had revenue of NOK 6.4m in 2024.

Where is OCEANFRONT AS based?

OCEANFRONT AS has its business address in Frei.

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.