BIZTRAC BETA
Activities of adventure companies

DUND AS

Org. no. 920253768 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK −238,000
Incorporated 2017
Share capital NOK 1.3m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−238k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).
  • Nylig endring 2026-04-25 Adresseendring registrert 2026-04-25.

DUND AS is registered as a limited company in Oslo, Oslo with organisation number 920253768. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2017. Registered share capital is NOK 1.3m, divided into 12800 shares. The company's stated purpose is: “Arrangere events i forbindelse med sportsarrangementer samt deltakelse i andre selskaper innenfor samme bransje. I tillegg skal selskapet drive med import og eksport, samt salg av blant annet frukt og grønnsaker.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK −238,000

Financial health · 2025

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

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

Who owns DUND AS?

AULIN-JANSSON HOLDING AS
DUND AS
NOK 0 rev. · NOK −20,000 profit

DUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DUND AS

Who owns DUND AS?

AULIN-JANSSON HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DUND AS?

DUND AS had revenue of NOK 0 in 2025.

Where is DUND AS based?

DUND AS has its business address in Oslo.

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.