BIZTRAC BETA
Computer programming activities

ENERGY MANAGER AS

Org. no. 912020991 Limited company (AS) Lindesnes Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 6.5m
Operating profit NOK −2.4m
Equity NOK 7.0m
Incorporated 2013
Share capital NOK 275,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,4 mill kr).

ENERGY MANAGER AS is registered as a limited company in Lindesnes, Agder with organisation number 912020991. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2013. Registered share capital is NOK 275,000, divided into 305836 shares. The company's stated purpose is: “Selskapets virksomhet er utvikling og salg av energirelaterte tjenester og verktøy.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.5m in revenue and NOK −2.4m in operating profit.

Key figures · 2024

Revenue
NOK 6.5m
Operating profit
NOK −2.4m
Equity
NOK 7.0m
Est. value
NOK 13.9m

Financial health · 2024

Liquidity
1.82
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
67.4%
Very good
Equity as a share of total capital

Who owns ENERGY MANAGER AS?

ENØK TOTAL AS
ENERGY MANAGER AS
NOK 6.5m rev. · NOK −2.4m profit

ENERGY MANAGER AS has 2 registered shareholders:

All shareholders and roles →

Group structure

ENERGY MANAGER AS er morselskap for 4 datterselskaper:

Frequently asked questions about ENERGY MANAGER AS

Who owns ENERGY MANAGER AS?

ENØK TOTAL AS is the largest registered owner, with 81.0%.

What is the revenue of ENERGY MANAGER AS?

ENERGY MANAGER AS had revenue of NOK 6.5m in 2024.

Who is the general manager of ENERGY MANAGER AS?

Rolf Olaf Halvorsen is registered as general manager of ENERGY MANAGER AS.

Where is ENERGY MANAGER AS based?

ENERGY MANAGER AS has its business address in Mandal.

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.