BIZTRAC BETA
Holiday and other short-stay accommodation

EXPLORE SJOA AS

Org. no. 926695460 Limited company (AS) Sel Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 3,000
Equity NOK 1.8m
Incorporated 2021
Employees 6
Share capital NOK 30,000

EXPLORE SJOA AS is registered as a limited company in Sel, Innlandet with organisation number 926695460. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2021 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Turisme og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 3,000
Equity
NOK 1.8m
Est. value
NOK 961,000

Financial health · 2024

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

Who owns EXPLORE SJOA AS?

CAMILLA SLETENGEN JACOBSEN
EXPLORE SJOA AS
NOK 7.4m rev. · NOK 3,000 profit

EXPLORE SJOA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EXPLORE SJOA AS own?

EXPLORE SJOA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EXPLORE SJOA AS

Who owns EXPLORE SJOA AS?

CAMILLA SLETENGEN JACOBSEN is the largest registered owner, with 50.0%.

What is the revenue of EXPLORE SJOA AS?

EXPLORE SJOA AS had revenue of NOK 7.4m in 2024.

Who is the general manager of EXPLORE SJOA AS?

Ole Magnus Bratvold Aamodt is registered as general manager of EXPLORE SJOA AS.

Where is EXPLORE SJOA AS based?

EXPLORE SJOA AS has its business address in Otta.

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.