biztrac. BETA
COMPANY REGISTER PROFILE
933909530 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠ARCTIC AURORA AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Holiday and other short-stay accommodation

ARCTIC AURORA AS

Org. no. 933909530 Limited company (AS) Skjervøy Incorporated 2024 In liquidation
Revenue 2025 NOK 190,000
Operating profit NOK 29,000
Equity NOK 65,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

ARCTIC AURORA AS is registered as a limited company in Skjervøy, Troms with organisation number 933909530. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Reiseliv.”. The most recent filed accounts, for the 2025 financial year, show NOK 190,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 190,000
▲ +121 %
Operating profit
NOK 29,000
▲ +31 %
Equity
NOK 65,000
▲ +55 %

Financial health · 2025

Liquidity
12.08
Very good
Current assets ÷ current liabilities
Profitability
38.5%
Very good
Return on total assets
Solidity
91.7%
Weak
Equity as a share of total capital

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

Who owns ARCTIC AURORA AS?

ARCTIC AURORA AS
NOK 190,000 rev. · NOK 29,000 profit

ARCTIC AURORA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARCTIC AURORA AS

Who owns ARCTIC AURORA AS?

Svein Roger Slettum Karlsen is the largest registered owner, with 50.0%.

What is the revenue of ARCTIC AURORA AS?

ARCTIC AURORA AS had revenue of NOK 190,000 in 2025.

Where is ARCTIC AURORA AS based?

ARCTIC AURORA AS has its business address in Arnøyhamn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.