BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

HAVSTRØM FJORDFISK TRADING AS

Org. no. 932693534 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 223,000
Operating profit NOK −4,000
Equity NOK 22,000
Incorporated 2023
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

HAVSTRØM FJORDFISK TRADING AS is registered as a limited company in Bærum, Akershus with organisation number 932693534. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Eksport av ferske og høykvalitets norske fiskeprodukter til kunder i Kina.”. The most recent filed accounts, for the 2025 financial year, show NOK 223,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 223,000
Operating profit
NOK −4,000
Equity
NOK 22,000
Est. value
NOK 83,000

Financial health · 2025

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAVSTRØM FJORDFISK TRADING AS?

HU CUI
HAVSTRØM FJORDFISK TRADING AS
NOK 223,000 rev. · NOK −4,000 profit

HAVSTRØM FJORDFISK TRADING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAVSTRØM FJORDFISK TRADING AS

Who owns HAVSTRØM FJORDFISK TRADING AS?

HU CUI is the largest registered owner, with 90.0%.

What is the revenue of HAVSTRØM FJORDFISK TRADING AS?

HAVSTRØM FJORDFISK TRADING AS had revenue of NOK 223,000 in 2025.

Where is HAVSTRØM FJORDFISK TRADING AS based?

HAVSTRØM FJORDFISK TRADING AS has its business address in Haslum.

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.