BIZTRAC BETA
Rental and operating of own or leased real estate

DUAA AS

Org. no. 988823791 Limited company (AS) Kristiansund Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −90,000
Equity NOK 6.0m
Incorporated 2005
Share capital NOK 72,000

Signals

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

DUAA AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 988823791. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 72,000, divided into 72240 shares. The company's stated purpose is: “Selv eller ved deltakelse i, eller i samarbeid med andre selskaper, å investere i aksjer, eiendom eller dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −90,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −90,000
Equity
NOK 6.0m
Est. value
NOK 9.7m

Financial health · 2024

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

Who owns DUAA AS?

OLAV KVALVÅG
DUAA AS
NOK 0 rev. · NOK −90,000 profit

DUAA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DUAA AS own?

DUAA AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about DUAA AS

Who owns DUAA AS?

OLAV KVALVÅG is the largest registered owner, with 100.0%.

What is the revenue of DUAA AS?

DUAA AS had revenue of NOK 0 in 2024.

Who is the general manager of DUAA AS?

Olav Kvalvåg is registered as general manager of DUAA AS.

Where is DUAA AS based?

DUAA AS has its business address in Kristiansund N.

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.