BIZTRAC BETA
Rental and operating of own or leased real estate

ES Eiendom AS

Org. no. 934551443 Limited company (AS) Lier Incorporated 1963 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 377,000
Equity NOK 7.1m
Incorporated 1963
Share capital NOK 5.6m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ES Eiendom AS is registered as a limited company in Lier, Buskerud with organisation number 934551443. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1963. Registered share capital is NOK 5.6m, divided into 56000 shares. The company's stated purpose is: “Eiendomsforvaltning og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 377,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 377,000
Equity
NOK 7.1m
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns ES Eiendom AS?

DALENG INVEST AS
ES Eiendom AS
NOK 4.9m rev. · NOK 377,000 profit

ES Eiendom AS has 2 registered shareholders:

All shareholders and roles →

Group structure

ES Eiendom AS er morselskap for 1 datterselskap:

Frequently asked questions about ES Eiendom AS

Who owns ES Eiendom AS?

DALENG INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of ES Eiendom AS?

ES Eiendom AS had revenue of NOK 4.9m in 2024.

Who is the general manager of ES Eiendom AS?

Ole Petter Daleng is registered as general manager of ES Eiendom AS.

Where is ES Eiendom AS based?

ES Eiendom AS has its business address in Tranby.

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.