BIZTRAC BETA
Activities of excursion and event organisers

ARCTIC OPEN EVENTS AS

Org. no. 930166103 Limited company (AS) Nordreisa Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 104,000
Equity NOK 107,000
Incorporated 2022
Share capital NOK 30,000

ARCTIC OPEN EVENTS AS is registered as a limited company in Nordreisa, Troms with organisation number 930166103. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arrangementsvirksomhet og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 104,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 104,000
Equity
NOK 107,000
Est. value
NOK 506,000

Financial health · 2025

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

Who owns ARCTIC OPEN EVENTS AS?

BJARNE HAGEN
ARCTIC OPEN EVENTS AS
NOK 2.0m rev. · NOK 104,000 profit

ARCTIC OPEN EVENTS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARCTIC OPEN EVENTS AS

Who owns ARCTIC OPEN EVENTS AS?

BJARNE HAGEN is the largest registered owner, with 50.0%.

What is the revenue of ARCTIC OPEN EVENTS AS?

ARCTIC OPEN EVENTS AS had revenue of NOK 2.0m in 2025.

Where is ARCTIC OPEN EVENTS AS based?

ARCTIC OPEN EVENTS AS has its business address in Storslett.

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.