BIZTRAC BETA
Activities of adventure companies

EXPLORE ÅLESUND AS

Org. no. 927905612 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 889,000
Equity NOK 524,000
Incorporated 2021
Employees 11
Share capital NOK 102,000

EXPLORE ÅLESUND AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 927905612. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2021 and has 11 registered employees. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Forskning, teknologiutvikling, bygging og drift av opplevelsesbaserte reiselivsprodukter. Selskapet skal også kunne delta i andre virksomheter med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 889,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 889,000
Equity
NOK 524,000
Est. value
NOK 3.1m

Financial health · 2024

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.8%
Good
Equity as a share of total capital

Who owns EXPLORE ÅLESUND AS?

EXPLORE HOLDING AS
EXPLORE ÅLESUND AS
NOK 3.3m rev. · NOK 889,000 profit

EXPLORE ÅLESUND AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EXPLORE ÅLESUND AS

Who owns EXPLORE ÅLESUND AS?

EXPLORE HOLDING AS is the largest registered owner, with 90.2%.

What is the revenue of EXPLORE ÅLESUND AS?

EXPLORE ÅLESUND AS had revenue of NOK 3.3m in 2024.

Who is the general manager of EXPLORE ÅLESUND AS?

Eirik Teigen Vaage is registered as general manager of EXPLORE ÅLESUND AS.

Where is EXPLORE ÅLESUND AS based?

EXPLORE ÅLESUND AS has its business address in Ålesund.

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.