BIZTRAC BETA
Operation of freshwater hatcheries

HYEN FISK HOLDING AS

Org. no. 927984725 Limited company (AS) Gloppen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 559,000
Operating profit NOK −1.7m
Equity NOK 136.6m
Incorporated 2021
Share capital NOK 787,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

HYEN FISK HOLDING AS is registered as a limited company in Gloppen, Vestland with organisation number 927984725. The business is classified under operation of freshwater hatcheries (NACE 03.222). The company was incorporated in 2021. Registered share capital is NOK 787,000, divided into 1458 shares. The company's stated purpose is: “Å drive næringsverksemnd gjennom oppdrett og sal av akvatiske organismer.”. The most recent filed accounts, for the 2024 financial year, show NOK 559,000 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 559,000
Operating profit
NOK −1.7m
Equity
NOK 136.6m
Est. value
NOK 124.3m

Financial health · 2024

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

Who owns HYEN FISK HOLDING AS?

AA-DJUPVIK INVEST AS
HYEN FISK HOLDING AS
NOK 559,000 rev. · NOK −1.7m profit

HYEN FISK HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does HYEN FISK HOLDING AS own?

HYEN FISK HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about HYEN FISK HOLDING AS

Who owns HYEN FISK HOLDING AS?

AA-DJUPVIK INVEST AS is the largest registered owner, with 28.7%.

What is the revenue of HYEN FISK HOLDING AS?

HYEN FISK HOLDING AS had revenue of NOK 559,000 in 2024.

Where is HYEN FISK HOLDING AS based?

HYEN FISK HOLDING AS has its business address in Hyen.

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.