BIZTRAC BETA
Holiday and other short-stay accommodation

GURVIKDAL HAVFISKESENTER AS

Org. no. 987423439 Limited company (AS) Gjerdrum Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 816,000
Equity NOK 3.9m
Incorporated 2004
Share capital NOK 1.1m

GURVIKDAL HAVFISKESENTER AS is registered as a limited company in Gjerdrum, Akershus with organisation number 987423439. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2004. Registered share capital is NOK 1.1m, divided into 1100 shares. The company's stated purpose is: “Reislivsvirksomhet samt kunne delta i andre selskaper innen for reiselivsbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 816,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 816,000
Equity
NOK 3.9m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns GURVIKDAL HAVFISKESENTER AS?

ASBJØRN RAGNAR GRØTTE
GURVIKDAL HAVFISKESENTER AS
NOK 3.3m rev. · NOK 816,000 profit

GURVIKDAL HAVFISKESENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GURVIKDAL HAVFISKESENTER AS

Who owns GURVIKDAL HAVFISKESENTER AS?

ASBJØRN RAGNAR GRØTTE is the largest registered owner, with 61.8%.

What is the revenue of GURVIKDAL HAVFISKESENTER AS?

GURVIKDAL HAVFISKESENTER AS had revenue of NOK 3.3m in 2025.

Who is the general manager of GURVIKDAL HAVFISKESENTER AS?

Karl Fredrik Johannesson is registered as general manager of GURVIKDAL HAVFISKESENTER AS.

Where is GURVIKDAL HAVFISKESENTER AS based?

GURVIKDAL HAVFISKESENTER AS has its business address in Gjerdrum.

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.