BIZTRAC BETA
Construction of residential and non-residential buildings

DUGAN HOLDING AS

Org. no. 991163441 Limited company (AS) Kvinesdal Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 482,000
Operating profit NOK −202,000
Equity NOK 1.1m
Incorporated 2007
Share capital NOK 100,000

Signals

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

DUGAN HOLDING AS is registered as a limited company in Kvinesdal, Agder with organisation number 991163441. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie og utleie av eiendommer med alt som hermed står i forbindelse, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 482,000 in revenue and NOK −202,000 in operating profit.

Key figures · 2024

Revenue
NOK 482,000
Operating profit
NOK −202,000
Equity
NOK 1.1m
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns DUGAN HOLDING AS?

TROND DUGAN
DUGAN HOLDING AS
NOK 482,000 rev. · NOK −202,000 profit

DUGAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DUGAN HOLDING AS own?

DUGAN HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about DUGAN HOLDING AS

Who owns DUGAN HOLDING AS?

TROND DUGAN is the largest registered owner, with 100.0%.

What is the revenue of DUGAN HOLDING AS?

DUGAN HOLDING AS had revenue of NOK 482,000 in 2024.

Where is DUGAN HOLDING AS based?

DUGAN HOLDING AS has its business address in Kvinesdal.

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.