BIZTRAC BETA
Steam and air conditioning supply

DRENGSRUDBEKKEN ENERGI AS

Org. no. 970974342 Limited company (AS) Asker Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 450,000
Equity NOK 16.0m
Incorporated 1994
Share capital NOK 500,000

DRENGSRUDBEKKEN ENERGI AS is registered as a limited company in Asker, Akershus with organisation number 970974342. The business is classified under steam and air conditioning supply (NACE 35.300). The company was incorporated in 1994. Registered share capital is NOK 500,000. The company's stated purpose is: “Produksjon, salg og distribusjon av energi og varmtvann fra grunnvannsbrønner.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 450,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 450,000
Equity
NOK 16.0m
Est. value
NOK 12.5m

Financial health · 2024

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

Who owns DRENGSRUDBEKKEN ENERGI AS?

OXER EIENDOM AS
DRENGSRUDBEKKEN ENERGI AS
NOK 2.9m rev. · NOK 450,000 profit

DRENGSRUDBEKKEN ENERGI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DRENGSRUDBEKKEN ENERGI AS er morselskap for 37 datterselskaper:

Frequently asked questions about DRENGSRUDBEKKEN ENERGI AS

Who owns DRENGSRUDBEKKEN ENERGI AS?

OXER EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of DRENGSRUDBEKKEN ENERGI AS?

DRENGSRUDBEKKEN ENERGI AS had revenue of NOK 2.9m in 2024.

Who is the general manager of DRENGSRUDBEKKEN ENERGI AS?

Erling Langeland is registered as general manager of DRENGSRUDBEKKEN ENERGI AS.

Where is DRENGSRUDBEKKEN ENERGI AS based?

DRENGSRUDBEKKEN ENERGI AS has its business address in Asker.

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.