BIZTRAC BETA
Operation of marine fish farms

OCEAN GEM AS

Org. no. 928487423 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 240,000
Operating profit NOK −707,000
Equity NOK −900,000
Incorporated 2021
Share capital NOK 651,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−900k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−707k kr).

OCEAN GEM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 928487423. The business is classified under operation of marine fish farms (NACE 03.211). The company was incorporated in 2021. Registered share capital is NOK 651,000, divided into 21700 shares. The company's stated purpose is: “Produksjon av matfisk, bløtdyr, krepsdyr og pigghuder i hav- og kystbasert akvakultur.”. The most recent filed accounts, for the 2024 financial year, show NOK 240,000 in revenue and NOK −707,000 in operating profit.

Key figures · 2024

Revenue
NOK 240,000
Operating profit
NOK −707,000
Equity
NOK −900,000

Financial health · 2024

Liquidity
6.68
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-20.1%
Weak
Equity as a share of total capital

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

Who owns OCEAN GEM AS?

ROFISK AS
OCEAN GEM AS
NOK 240,000 rev. · NOK −707,000 profit

OCEAN GEM AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about OCEAN GEM AS

Who owns OCEAN GEM AS?

ROFISK AS is the largest registered owner, with 26.7%.

What is the revenue of OCEAN GEM AS?

OCEAN GEM AS had revenue of NOK 240,000 in 2024.

Who is the general manager of OCEAN GEM AS?

Bård Sindre Skarshaug is registered as general manager of OCEAN GEM AS.

Where is OCEAN GEM AS based?

OCEAN GEM AS has its business address in Harøy.

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.