BIZTRAC BETA
Rental and leasing of recreational and sports goods

ARCTIC FISHING SOMMARØY AS

Org. no. 919216506 Limited company (AS) Tromsø Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 1.0m
Equity NOK 861,000
Incorporated 2017
Share capital NOK 1.0m

ARCTIC FISHING SOMMARØY AS is registered as a limited company in Tromsø, Troms with organisation number 919216506. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2017. Registered share capital is NOK 1.0m, divided into 10005 shares. The company's stated purpose is: “Utleie av båt og bolig til turister. Selskapet skal også kunne delta i andre foretak med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 1.0m
Equity
NOK 861,000
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns ARCTIC FISHING SOMMARØY AS?

MARKUS HAAKE
ARCTIC FISHING SOMMARØY AS
NOK 2.8m rev. · NOK 1.0m profit

ARCTIC FISHING SOMMARØY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARCTIC FISHING SOMMARØY AS

Who owns ARCTIC FISHING SOMMARØY AS?

MARKUS HAAKE is the largest registered owner, with 50.1%.

What is the revenue of ARCTIC FISHING SOMMARØY AS?

ARCTIC FISHING SOMMARØY AS had revenue of NOK 2.8m in 2024.

Who is the general manager of ARCTIC FISHING SOMMARØY AS?

Markus Haake is registered as general manager of ARCTIC FISHING SOMMARØY AS.

Where is ARCTIC FISHING SOMMARØY AS based?

ARCTIC FISHING SOMMARØY AS has its business address in Kvaløya.

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.