BIZTRAC BETA
Growing of other non-perennial crops

ENERGEIA MÆHLUM AS

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

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−156k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−76k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ENERGEIA MÆHLUM AS is registered as a limited company in Oslo, Oslo with organisation number 929626133. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie, finansiere, drifte, kjøpe og selge 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 · 2024

Operating profit
NOK −76,000
Equity
NOK −156,000

Financial health · 2024

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

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

Who owns ENERGEIA MÆHLUM AS?

ENERGEIA NORWAY HOLDING AS
ENERGEIA MÆHLUM AS
· NOK −76,000 profit

ENERGEIA MÆHLUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENERGEIA MÆHLUM AS

Who owns ENERGEIA MÆHLUM AS?

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

Where is ENERGEIA MÆHLUM AS based?

ENERGEIA MÆHLUM 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.