biztrac. BETA
COMPANY REGISTER PROFILE
929633911 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ENERGEIA STORE NØKLEBERG AS

Org. no. 929633911 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −66,000
Equity NOK −366,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

ENERGEIA STORE NØKLEBERG AS is registered as a limited company in Oslo, Oslo with organisation number 929633911. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle, bygge, eie, finansiere og drifte solparker, og virksomhet som står i naturlig sammenheng med dette, herunder eierskap i tilsvarende selskaper. Selskapets virksomhet er også jordbruksproduksjon herunder salg av gress og høy samt utleie av innmarksbeite.”.

Key figures · 2025

Operating profit
NOK −66,000
▼ −3 %
Equity
NOK −366,000
▼ −126 %

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
-1.3%
Not satisfactory
Return on total assets
Solidity
-6.4%
Weak
Equity as a share of total capital

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

Who owns ENERGEIA STORE NØKLEBERG AS?

ENERGEIA STORE NØKLEBERG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENERGEIA STORE NØKLEBERG AS

Who owns ENERGEIA STORE NØKLEBERG AS?

ENERGEIA NORWAY HOLDING AS is the largest registered owner, with 51.0%.

Where is ENERGEIA STORE NØKLEBERG AS based?

ENERGEIA STORE NØKLEBERG 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.