BIZTRAC BETA
Other technical consultancy

RAMOCEAN AS

Org. no. 925322121 Limited company (AS) Horten Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −285,000
Equity NOK 135,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−285k kr).

RAMOCEAN AS is registered as a limited company in Horten, Vestfold with organisation number 925322121. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Å drive med promotering og løsninger for fornybar energi basert på hav-vind, hav, og flytende installasjoner, og alt som står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −285,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −285,000
Equity
NOK 135,000
Est. value
NOK 220,000

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.5%
Good
Equity as a share of total capital

Who owns RAMOCEAN AS?

HÅKON RAMDE
RAMOCEAN AS
NOK 0 rev. · NOK −285,000 profit

RAMOCEAN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RAMOCEAN AS own?

RAMOCEAN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RAMOCEAN AS

Who owns RAMOCEAN AS?

HÅKON RAMDE is the largest registered owner, with 50.0%.

What is the revenue of RAMOCEAN AS?

RAMOCEAN AS had revenue of NOK 0 in 2025.

Who is the general manager of RAMOCEAN AS?

Øivind Ramde is registered as general manager of RAMOCEAN AS.

Where is RAMOCEAN AS based?

RAMOCEAN AS has its business address in Åsgårdstrand.

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.