BIZTRAC BETA
COMPANY REGISTER PROFILE
925878804 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

DALENVEIEN BOLIG AS

Org. no. 925878804 Limited company (AS) Lier Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −222,000
Equity NOK 712,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−222k kr).

DALENVEIEN BOLIG AS is registered as a limited company in Lier, Buskerud with organisation number 925878804. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle boligprosjekt i Dalenveien.”.

Key figures · 2025

Operating profit
NOK −222,000
▼ −33 %
Equity
NOK 712,000
▼ −21 %
Est. value
NOK 650,000

Financial health · 2025

Liquidity
7.94
Very good
Current assets ÷ current liabilities
Profitability
-11.2%
Not satisfactory
Return on total assets
Solidity
35.9%
Good
Equity as a share of total capital

Who owns DALENVEIEN BOLIG AS?

DALENVEIEN BOLIG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DALENVEIEN BOLIG AS

Who owns DALENVEIEN BOLIG AS?

WELHAVEN JR HOLDING AS is the largest registered owner, with 50.0%.

Where is DALENVEIEN BOLIG AS based?

DALENVEIEN BOLIG AS has its business address in Lier.

Property

Business address Flåtansvingen 52, 3413 Lier
Cadastral unit 3312-36/42/0/0
Building Enebolig · 3 units

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.