BIZTRAC BETA
Rental and operating of own or leased real estate

ENGDALHEIM EIENDOM AS

Org. no. 922759227 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 269,000
Operating profit NOK 219,000
Equity NOK 2.2m
Incorporated 2019
Share capital NOK 60,000

ENGDALHEIM EIENDOM AS is registered as a limited company in Asker, Akershus with organisation number 922759227. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom samt forvaltning av fast eiendom gjennom utleie. Selskapet kan også ha interesser i andre virksomheter og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 269,000 in revenue and NOK 219,000 in operating profit.

Key figures · 2025

Revenue
NOK 269,000
Operating profit
NOK 219,000
Equity
NOK 2.2m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns ENGDALHEIM EIENDOM AS?

OLE ERIK ØSTRENG
ENGDALHEIM EIENDOM AS
NOK 269,000 rev. · NOK 219,000 profit

ENGDALHEIM EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENGDALHEIM EIENDOM AS

Who owns ENGDALHEIM EIENDOM AS?

OLE ERIK ØSTRENG is the largest registered owner, with 33.3%.

What is the revenue of ENGDALHEIM EIENDOM AS?

ENGDALHEIM EIENDOM AS had revenue of NOK 269,000 in 2025.

Where is ENGDALHEIM EIENDOM AS based?

ENGDALHEIM EIENDOM AS has its business address in Nesbru.

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.