BIZTRAC BETA
Operation of marine fish farms

BLOM SETTEFISK AS

Org. no. 936100112 Limited company (AS) Øygarden Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 77.5m
Operating profit NOK 8.5m
Equity NOK 71.1m
Incorporated 1984
Employees 27
Share capital NOK 918,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BLOM SETTEFISK AS is registered as a limited company in Øygarden, Vestland with organisation number 936100112. The business is classified under operation of marine fish farms (NACE 03.211). The company was incorporated in 1984 and has 27 registered employees. Registered share capital is NOK 918,000, divided into 918 shares. The company's stated purpose is: “Oppdrett av fisk og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 77.5m in revenue and NOK 8.5m in operating profit.

Key figures · 2024

Revenue
NOK 77.5m
Operating profit
NOK 8.5m
Equity
NOK 71.1m
Est. value
NOK 58.8m

Financial health · 2024

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

Who owns BLOM SETTEFISK AS?

BLOM FISKEOPPDRETT AS
BLOM SETTEFISK AS
NOK 77.5m rev. · NOK 8.5m profit

BLOM SETTEFISK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLOM SETTEFISK AS

Who owns BLOM SETTEFISK AS?

BLOM FISKEOPPDRETT AS is the largest registered owner, with 72.3%.

What is the revenue of BLOM SETTEFISK AS?

BLOM SETTEFISK AS had revenue of NOK 77.5m in 2024.

Who is the general manager of BLOM SETTEFISK AS?

Øyvind Blom is registered as general manager of BLOM SETTEFISK AS.

Where is BLOM SETTEFISK AS based?

BLOM SETTEFISK AS has its business address in Rong.

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.