BIZTRAC BETA
Activities of excursion and event organisers

BARENTS SEA ADVENTURE AS

Org. no. 930579076 Limited company (AS) Hammerfest Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK −744
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−744 kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

BARENTS SEA ADVENTURE AS is registered as a limited company in Hammerfest, Finnmark with organisation number 930579076. 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: “Fisketurisme og Fiskebåtbygging. Ny design, modell og teknologi på fiskebåtbygging.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK −744

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns BARENTS SEA ADVENTURE AS?

Tomi Dahl
BARENTS SEA ADVENTURE AS
NOK 0 rev. · NOK −10,000 profit

BARENTS SEA ADVENTURE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARENTS SEA ADVENTURE AS

Who owns BARENTS SEA ADVENTURE AS?

Tomi Dahl is the largest registered owner, with 100.0%.

What is the revenue of BARENTS SEA ADVENTURE AS?

BARENTS SEA ADVENTURE AS had revenue of NOK 0 in 2024.

Where is BARENTS SEA ADVENTURE AS based?

BARENTS SEA ADVENTURE AS has its business address in Hammerfest.

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.