BIZTRAC BETA
Business and other management consultancy activities

EDDA ENERGY AS

Org. no. 922015171 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK −24,000
Incorporated 2018
Share capital NOK 150,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−24k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

EDDA ENERGY AS is registered as a limited company in Oslo, Oslo with organisation number 922015171. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Forvaltning av alternative investeringsfond og relatert virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK −24,000

Financial health · 2025

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

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

Who owns EDDA ENERGY AS?

TOR KLAVENESS
EDDA ENERGY AS
NOK 0 rev. · NOK −9,000 profit

EDDA ENERGY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EDDA ENERGY AS

Who owns EDDA ENERGY AS?

TOR KLAVENESS is the largest registered owner, with 100.0%.

What is the revenue of EDDA ENERGY AS?

EDDA ENERGY AS had revenue of NOK 0 in 2025.

Who is the general manager of EDDA ENERGY AS?

Tor Klaveness is registered as general manager of EDDA ENERGY AS.

Where is EDDA ENERGY AS based?

EDDA ENERGY AS has its business address in Oslo.

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.