BIZTRAC BETA
Development of building projects

DVERGSNES UTVIKLING AS

Org. no. 820492412 Limited company (AS) Kristiansand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 200,000
Operating profit NOK −11,000
Equity NOK −33,000
Incorporated 2018
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−33k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

DVERGSNES UTVIKLING AS is registered as a limited company in Kristiansand, Agder with organisation number 820492412. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling, utleie og salg av eiendommer og aksjer, samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 200,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 200,000
Operating profit
NOK −11,000
Equity
NOK −33,000

Financial health · 2025

Liquidity
79.30
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.1%
Weak
Equity as a share of total capital

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

Who owns DVERGSNES UTVIKLING AS?

REMCO AS
DVERGSNES UTVIKLING AS
NOK 200,000 rev. · NOK −11,000 profit

DVERGSNES UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DVERGSNES UTVIKLING AS

Who owns DVERGSNES UTVIKLING AS?

REMCO AS is the largest registered owner, with 50.0%.

What is the revenue of DVERGSNES UTVIKLING AS?

DVERGSNES UTVIKLING AS had revenue of NOK 200,000 in 2025.

Where is DVERGSNES UTVIKLING AS based?

DVERGSNES UTVIKLING AS has its business address in Kristiansand S.

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.