BIZTRAC BETA
COMPANY REGISTER PROFILE
821689902 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

DCK HOLDING AS

Org. no. 821689902 Limited company (AS) Hamar Incorporated 2018 Active
Ownership graph ↗
Equity NOK 23,000
Incorporated 2018
Share capital NOK 30,000

DCK HOLDING AS is registered as a limited company in Hamar, Innlandet with organisation number 821689902. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Deltakelse i andre selskaper, samt kjøp, salg og utvikling av eiendommer og det som ellers naturlig hører til dette.”.

Key figures · 2025

Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2025

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

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

Who owns DCK HOLDING AS?

DCK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DCK HOLDING AS own?

DCK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DCK HOLDING AS

Who owns DCK HOLDING AS?

DAN CHRISTER KAULUM is the largest registered owner, with 100.0%.

Where is DCK HOLDING AS based?

DCK HOLDING AS has its business address in Hamar.

Property

Business address Torgny Segerstedts gate 37, 2319 Hamar
Cadastral unit 3403-1/2052/0/0
Building Enebolig · 1 unit

8 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.