BIZTRAC BETA
Rental and operating of own or leased real estate

DAHLE EIENDOM AS

Org. no. 924797843 Limited company (AS) Kristiansand Incorporated 1975 Active
Ownership graph ↗
Revenue 2024 NOK 12.2m
Operating profit NOK −677,000
Equity NOK −3.4m
Incorporated 1975
Share capital NOK 2.5m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−677k kr).

DAHLE EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 924797843. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1975. Registered share capital is NOK 2.5m, divided into 2500000 shares. The company's stated purpose is: “Erverv og forvaltning av fast eiendom, kjøp og salg av aksjer samt avgivelse av garantier og del- tagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.2m in revenue and NOK −677,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.2m
Operating profit
NOK −677,000
Equity
NOK −3.4m

Financial health · 2024

Liquidity
2.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DAHLE EIENDOM AS?

KAMBRIUM AS
DAHLE EIENDOM AS
NOK 12.2m rev. · NOK −677,000 profit

DAHLE EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DAHLE EIENDOM AS

Who owns DAHLE EIENDOM AS?

KAMBRIUM AS is the largest registered owner, with 49.7%.

What is the revenue of DAHLE EIENDOM AS?

DAHLE EIENDOM AS had revenue of NOK 12.2m in 2024.

Where is DAHLE EIENDOM AS based?

DAHLE EIENDOM AS has its business address in Kristiansand S.

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.