BIZTRAC BETA
Operation of freshwater hatcheries

BRAKEDAL SETTEFISK AS

Org. no. 958716796 Limited company (AS) Bømlo Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 694,000
Operating profit NOK −879,000
Equity NOK 2.5m
Incorporated 1990
Share capital NOK 510,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−879k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRAKEDAL SETTEFISK AS is registered as a limited company in Bømlo, Vestland with organisation number 958716796. The business is classified under operation of freshwater hatcheries (NACE 03.222). The company was incorporated in 1990. Registered share capital is NOK 510,000, divided into 510 shares. The company's stated purpose is: “Smoltklekkeri og omsetning av smolt.”. The most recent filed accounts, for the 2024 financial year, show NOK 694,000 in revenue and NOK −879,000 in operating profit.

Key figures · 2024

Revenue
NOK 694,000
Operating profit
NOK −879,000
Equity
NOK 2.5m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns BRAKEDAL SETTEFISK AS?

FYLKESNES HOLDING AS
BRAKEDAL SETTEFISK AS
NOK 694,000 rev. · NOK −879,000 profit

BRAKEDAL SETTEFISK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRAKEDAL SETTEFISK AS

Who owns BRAKEDAL SETTEFISK AS?

FYLKESNES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRAKEDAL SETTEFISK AS?

BRAKEDAL SETTEFISK AS had revenue of NOK 694,000 in 2024.

Where is BRAKEDAL SETTEFISK AS based?

BRAKEDAL SETTEFISK AS has its business address in Rubbestadneset.

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.