BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

HAARBERG SEAFOOD AS

Org. no. 988959626 Limited company (AS) Modum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −52,000
Equity NOK 4.5m
Incorporated 2005
Share capital NOK 450,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−52k kr).

HAARBERG SEAFOOD AS is registered as a limited company in Modum, Buskerud with organisation number 988959626. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2005. Registered share capital is NOK 450,000, divided into 450 shares. The company's stated purpose is: “Selskapets formål er handel med næringsmidler samt deltagelse som aksjonær eller på annen måte i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −52,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −52,000
Equity
NOK 4.5m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns HAARBERG SEAFOOD AS?

ESPEN HAARBERG
HAARBERG SEAFOOD AS
NOK 0 rev. · NOK −52,000 profit

HAARBERG SEAFOOD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HAARBERG SEAFOOD AS own?

HAARBERG SEAFOOD AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HAARBERG SEAFOOD AS

Who owns HAARBERG SEAFOOD AS?

ESPEN HAARBERG is the largest registered owner, with 50.0%.

What is the revenue of HAARBERG SEAFOOD AS?

HAARBERG SEAFOOD AS had revenue of NOK 0 in 2024.

Where is HAARBERG SEAFOOD AS based?

HAARBERG SEAFOOD AS has its business address in Geithus.

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.