BIZTRAC BETA
Development of building projects

DAHLE OG SØRLIE EIENDOM AS

Org. no. 819221022 Limited company (AS) Sarpsborg Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −38,000
Equity NOK 43.8m
Incorporated 2017
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−38k kr).
  • Nylig endring 2026-05-20 Aksjekapital registrert 2026-05-20.

DAHLE OG SØRLIE EIENDOM AS is registered as a limited company in Sarpsborg, Østfold with organisation number 819221022. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Å erverve, utvikle og drive fast eiendom, erverve og forvalte aksjer, samt å delta i andre virksomheter med tilsvarende eller lignende formål.”.

Key figures · 2024

Operating profit
NOK −38,000
Equity
NOK 43.8m
Est. value
NOK 30.5m

Financial health · 2024

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

Who owns DAHLE OG SØRLIE EIENDOM AS?

DAHLE EIENDOM HOLDING AS
DAHLE OG SØRLIE EIENDOM AS
· NOK −38,000 profit

DAHLE OG SØRLIE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does DAHLE OG SØRLIE EIENDOM AS own?

DAHLE OG SØRLIE EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

DAHLE OG SØRLIE EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about DAHLE OG SØRLIE EIENDOM AS

Who owns DAHLE OG SØRLIE EIENDOM AS?

DAHLE EIENDOM HOLDING AS is the largest registered owner, with 50.0%.

Where is DAHLE OG SØRLIE EIENDOM AS based?

DAHLE OG SØRLIE EIENDOM AS has its business address in Sarpsborg.

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.