BIZTRAC BETA
Other captive investment companies

VEGARD DALEN HOLDING AS

Org. no. 997377370 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 377,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

VEGARD DALEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 997377370. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 377,000
Est. value
NOK 344,000

Financial health · 2025

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

Who owns VEGARD DALEN HOLDING AS?

VEGARD LILLESETH DALEN
VEGARD DALEN HOLDING AS
NOK 0 rev. · NOK −4,000 profit

VEGARD DALEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VEGARD DALEN HOLDING AS own?

VEGARD DALEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VEGARD DALEN HOLDING AS

Who owns VEGARD DALEN HOLDING AS?

VEGARD LILLESETH DALEN is the largest registered owner, with 100.0%.

What is the revenue of VEGARD DALEN HOLDING AS?

VEGARD DALEN HOLDING AS had revenue of NOK 0 in 2025.

Where is VEGARD DALEN HOLDING AS based?

VEGARD DALEN HOLDING AS has its business address in Oslo.

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.