biztrac. BETA
COMPANY REGISTER PROFILE
996607488 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

DUNKIK AS

Org. no. 996607488 Limited company (AS) Gjesdal Incorporated 2011 Active
Revenue 2025 NOK 50,000
Operating profit NOK −25,000
Equity NOK 6.1m
Incorporated 2011
Share capital NOK 100,000

Signals

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

DUNKIK AS is registered as a limited company in Gjesdal, Rogaland with organisation number 996607488. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel, investerings- og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 50,000
▼ −6 %
Operating profit
NOK −25,000
▲ +55 %
Equity
NOK 6.1m
▼ −6 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
57.32
Very good
Current assets ÷ current liabilities
Profitability
2.3%
Weak
Return on total assets
Solidity
98.3%
Very good
Equity as a share of total capital

Who owns DUNKIK AS?

DUNKIK AS has 3 registered shareholders:

All shareholders and roles →

Which companies does DUNKIK AS own?

DUNKIK AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about DUNKIK AS

Who owns DUNKIK AS?

Knud Peder Daugaard is the largest registered owner, with 60.0%.

What is the revenue of DUNKIK AS?

DUNKIK AS had revenue of NOK 50,000 in 2025.

Who is the general manager of DUNKIK AS?

Knud Peder Daugaard is registered as general manager of DUNKIK AS.

Where is DUNKIK AS based?

DUNKIK AS has its business address in Ålgård.

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

Report a problem

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