BIZTRAC BETA
Holiday and other short-stay accommodation

SOMMERSEL FISHING CAMP AS

Org. no. 915126685 Limited company (AS) Hamarøy Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 669,000
Equity NOK 1.1m
Incorporated 2015
Share capital NOK 30,000

SOMMERSEL FISHING CAMP AS is registered as a limited company in Hamarøy, Nordland with organisation number 915126685. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive fisketurisme, kjøp, eie og utleie av eiendom og båter, og annet som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 669,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 669,000
Equity
NOK 1.1m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns SOMMERSEL FISHING CAMP AS?

MARCO GRANSEE
SOMMERSEL FISHING CAMP AS
NOK 1.7m rev. · NOK 669,000 profit

SOMMERSEL FISHING CAMP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOMMERSEL FISHING CAMP AS

Who owns SOMMERSEL FISHING CAMP AS?

MARCO GRANSEE is the largest registered owner, with 37.5%.

What is the revenue of SOMMERSEL FISHING CAMP AS?

SOMMERSEL FISHING CAMP AS had revenue of NOK 1.7m in 2024.

Where is SOMMERSEL FISHING CAMP AS based?

SOMMERSEL FISHING CAMP AS has its business address in Tranø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.