BIZTRAC BETA
Other technical consultancy

ENNY AS

Org. no. 930453781 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 14.8m
Operating profit NOK −9.9m
Equity NOK 8.1m
Incorporated 2022
Employees 8
Share capital NOK 3.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9,9 mill kr).
  • Nylig endring 2026-05-18 Aksjekapital registrert 2026-05-18.

ENNY AS is registered as a limited company in Bærum, Akershus with organisation number 930453781. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 3.0m, divided into 300000 shares. The company's stated purpose is: “Eierskap og drift av energisystemer.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.8m in revenue and NOK −9.9m in operating profit.

Key figures · 2024

Revenue
NOK 14.8m
Operating profit
NOK −9.9m
Equity
NOK 8.1m
Est. value
NOK 19.5m

Financial health · 2024

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

Who owns ENNY AS?

OBOS AKSJEINVESTERINGER AS
ENNY AS
NOK 14.8m rev. · NOK −9.9m profit

ENNY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ENNY AS own?

ENNY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENNY AS

Who owns ENNY AS?

OBOS AKSJEINVESTERINGER AS is the largest registered owner, with 100.0%.

What is the revenue of ENNY AS?

ENNY AS had revenue of NOK 14.8m in 2024.

Who is the general manager of ENNY AS?

Terje Borkenhagen is registered as general manager of ENNY AS.

Where is ENNY AS based?

ENNY AS has its business address in Lysaker.

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.