BIZTRAC BETA
Other tour operator activities

NORRØNA ADVENTURE AS

Org. no. 930067539 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −2.2m
Equity NOK 8.5m
Incorporated 2022
Share capital NOK 73,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NORRØNA ADVENTURE AS is registered as a limited company in Bærum, Akershus with organisation number 930067539. The business is classified under other tour operator activities (NACE 79.122). The company was incorporated in 2022. Registered share capital is NOK 73,000, divided into 3456 shares. The company's stated purpose is: “Handel og alt som står i forbindelse hermed, samt deltakelse i annen virksomhet, herunder investering i aksjer, verdipapirer og fast eiendom.”.

Key figures · 2024

Operating profit
NOK −2.2m
Equity
NOK 8.5m
Est. value
NOK 12.3m

Financial health · 2024

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.7%
Good
Equity as a share of total capital

Who owns NORRØNA ADVENTURE AS?

ARKTIS HOLDING AS
NORRØNA ADVENTURE AS
· NOK −2.2m profit

NORRØNA ADVENTURE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NORRØNA ADVENTURE AS own?

NORRØNA ADVENTURE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NORRØNA ADVENTURE AS

Who owns NORRØNA ADVENTURE AS?

ARKTIS HOLDING AS is the largest registered owner, with 96.7%.

Who is the general manager of NORRØNA ADVENTURE AS?

Jørgen Jørgensen is registered as general manager of NORRØNA ADVENTURE AS.

Where is NORRØNA ADVENTURE AS based?

NORRØNA ADVENTURE AS has its business address in Lysaker.

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.