BIZTRAC BETA
Marine fishing

GULLFESKEN AS

Org. no. 991404074 Limited company (AS) Senja Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 61.6m
Operating profit NOK 12.7m
Equity NOK 23.5m
Incorporated 2007
Employees 56
Share capital NOK 861,000

GULLFESKEN AS is registered as a limited company in Senja, Troms with organisation number 991404074. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2007 and has 56 registered employees. Registered share capital is NOK 861,000, divided into 861 shares. The company's stated purpose is: “Kjøp og drift av fiskefartøy, tjenester innen akvakultur og virksomhet for øvrig som er naturlig for selskapet og som kommer selskapet til gode.”. The most recent filed accounts, for the 2024 financial year, show NOK 61.6m in revenue and NOK 12.7m in operating profit.

Key figures · 2024

Revenue
NOK 61.6m
Operating profit
NOK 12.7m
Equity
NOK 23.5m
Est. value
NOK 43.0m

Financial health · 2024

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.8%
Good
Equity as a share of total capital

Who owns GULLFESKEN AS?

PHPAULSEN HOLDING AS
GULLFESKEN AS
NOK 61.6m rev. · NOK 12.7m profit

GULLFESKEN AS has 8 registered shareholders:

All shareholders and roles →

Which companies does GULLFESKEN AS own?

GULLFESKEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GULLFESKEN AS

Who owns GULLFESKEN AS?

PHPAULSEN HOLDING AS is the largest registered owner, with 41.0%.

What is the revenue of GULLFESKEN AS?

GULLFESKEN AS had revenue of NOK 61.6m in 2024.

Who is the general manager of GULLFESKEN AS?

Peter Hermod Hansen Paulsen is registered as general manager of GULLFESKEN AS.

Where is GULLFESKEN AS based?

GULLFESKEN AS has its business address in Botnhamn.

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.