BIZTRAC BETA
Other technical consultancy

SVEPRO OCEAN ENERGY AS

Org. no. 992668326 Limited company (AS) Aure Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −118,000
Incorporated 2008
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−118k kr).

SVEPRO OCEAN ENERGY AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 992668326. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2008. Registered share capital is NOK 150,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av bølgekraftteknologi for markedet i hele verden og herunder alt som kreves og som kan utnyttes i forbindelse med dette. Utstedelse av lisensproduksjon av bølgekraft.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −118,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns SVEPRO OCEAN ENERGY AS?

ERNST JOHNNY SVELUND
SVEPRO OCEAN ENERGY AS
NOK 0 rev. · NOK 0 profit

SVEPRO OCEAN ENERGY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVEPRO OCEAN ENERGY AS

Who owns SVEPRO OCEAN ENERGY AS?

ERNST JOHNNY SVELUND is the largest registered owner, with 89.0%.

What is the revenue of SVEPRO OCEAN ENERGY AS?

SVEPRO OCEAN ENERGY AS had revenue of NOK 0 in 2024.

Where is SVEPRO OCEAN ENERGY AS based?

SVEPRO OCEAN ENERGY AS has its business address in Tustna.

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.