BIZTRAC BETA
Other captive investment companies

DAG CHRISTIAN NIELSEN HOLDING AS

Org. no. 993786217 Limited company (AS) Kristiansand Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 10.4m
Incorporated 2009
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

DAG CHRISTIAN NIELSEN HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 993786217. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 160000 shares. The company's stated purpose is: “Å erverve, eie og selge eierandeler i andre selskaper og virksomheter.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK 10.4m
Est. value
NOK 8.5m

Financial health · 2024

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

Who owns DAG CHRISTIAN NIELSEN HOLDING AS?

DAG CHRISTIAN NIELSEN
DAG CHRISTIAN NIELSEN HOLDING AS
· NOK −5,000 profit

DAG CHRISTIAN NIELSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DAG CHRISTIAN NIELSEN HOLDING AS own?

DAG CHRISTIAN NIELSEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about DAG CHRISTIAN NIELSEN HOLDING AS

Who owns DAG CHRISTIAN NIELSEN HOLDING AS?

DAG CHRISTIAN NIELSEN is the largest registered owner, with 100.0%.

Who is the general manager of DAG CHRISTIAN NIELSEN HOLDING AS?

Dag Christian Nielsen is registered as general manager of DAG CHRISTIAN NIELSEN HOLDING AS.

Where is DAG CHRISTIAN NIELSEN HOLDING AS based?

DAG CHRISTIAN NIELSEN HOLDING AS has its business address in Søgne.

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.