BIZTRAC BETA
Trade of electricity

KRAGERØ SJØENERGI AS

Org. no. 925446718 Limited company (AS) Kragerø Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 61,000
Operating profit NOK −640,000
Equity NOK 638,000
Incorporated 2020
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−640k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KRAGERØ SJØENERGI AS is registered as a limited company in Kragerø, Telemark with organisation number 925446718. The business is classified under trade of electricity (NACE 35.150). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Å drive virksomhet vedrørende omsetning av elektrisk kraft samt annen virksomhet i forbindelse med dette formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 61,000 in revenue and NOK −640,000 in operating profit.

Key figures · 2024

Revenue
NOK 61,000
Operating profit
NOK −640,000
Equity
NOK 638,000
Est. value
NOK 702,000

Financial health · 2024

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

Who owns KRAGERØ SJØENERGI AS?

KRAGERØ UTBYGGING AS
KRAGERØ SJØENERGI AS
NOK 61,000 rev. · NOK −640,000 profit

KRAGERØ SJØENERGI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRAGERØ SJØENERGI AS

Who owns KRAGERØ SJØENERGI AS?

KRAGERØ UTBYGGING AS is the largest registered owner, with 100.0%.

What is the revenue of KRAGERØ SJØENERGI AS?

KRAGERØ SJØENERGI AS had revenue of NOK 61,000 in 2024.

Where is KRAGERØ SJØENERGI AS based?

KRAGERØ SJØENERGI AS has its business address in Kragerø.

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.