BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

FRAM SEAFOOD AS

Org. no. 820436482 Limited company (AS) Bodø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.3bn
Operating profit NOK 9.2m
Equity NOK 75.9m
Incorporated 2018
Employees 16
Share capital NOK 5.6m

FRAM SEAFOOD AS is registered as a limited company in Bodø, Nordland with organisation number 820436482. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2018 and has 16 registered employees. Registered share capital is NOK 5.6m, divided into 555554 shares. The company's stated purpose is: “Kjøp og salg av fiskeprodukter, deltakelse i annen virksomhet, samt hva som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3bn in revenue and NOK 9.2m in operating profit.

Key figures · 2024

Revenue
NOK 1.3bn
Operating profit
NOK 9.2m
Equity
NOK 75.9m
Est. value
NOK 72.6m

Financial health · 2024

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

Who owns FRAM SEAFOOD AS?

NYHAMN AS
FRAM SEAFOOD AS
NOK 1.3bn rev. · NOK 9.2m profit

FRAM SEAFOOD AS has 9 registered shareholders:

All shareholders and roles →

Which companies does FRAM SEAFOOD AS own?

FRAM SEAFOOD AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about FRAM SEAFOOD AS

Who owns FRAM SEAFOOD AS?

NYHAMN AS is the largest registered owner, with 24.0%.

What is the revenue of FRAM SEAFOOD AS?

FRAM SEAFOOD AS had revenue of NOK 1.3bn in 2024.

Who is the general manager of FRAM SEAFOOD AS?

Ole Kristian Kjellbakk is registered as general manager of FRAM SEAFOOD AS.

Where is FRAM SEAFOOD AS based?

FRAM SEAFOOD AS has its business address in Bodø.

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.