BIZTRAC BETA
Activities of excursion and event organisers

OPPLEV SOLBAKKE AS

Org. no. 928582787 Limited company (AS) Hvaler Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 47,000
Operating profit NOK −1,000
Equity NOK 13,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1k kr).

OPPLEV SOLBAKKE AS is registered as a limited company in Hvaler, Østfold with organisation number 928582787. 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 30000 shares. The company's stated purpose is: “Innholdsproduksjon og arrangør av aktiviteter og opplevelser for bedrift- og privatmarkedet med tilstøtende virksomhet, samt kjøp og salg av verdipapirer og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 47,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 47,000
Operating profit
NOK −1,000
Equity
NOK 13,000
Est. value
NOK 36,000

Financial health · 2024

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

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

Who owns OPPLEV SOLBAKKE AS?

JAN JOACHIM JOHANNESSEN
OPPLEV SOLBAKKE AS
NOK 47,000 rev. · NOK −1,000 profit

OPPLEV SOLBAKKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OPPLEV SOLBAKKE AS

Who owns OPPLEV SOLBAKKE AS?

JAN JOACHIM JOHANNESSEN is the largest registered owner, with 50.0%.

What is the revenue of OPPLEV SOLBAKKE AS?

OPPLEV SOLBAKKE AS had revenue of NOK 47,000 in 2024.

Where is OPPLEV SOLBAKKE AS based?

OPPLEV SOLBAKKE AS has its business address in Vesterøy.

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.