BIZTRAC BETA
Freezing and further processing of fish, crustaceans and molluscs

BLEIK FISK AS

Org. no. 917030847 Limited company (AS) Andøy Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 346,000
Equity NOK 3.2m
Incorporated 2016
Share capital NOK 1.9m

BLEIK FISK AS is registered as a limited company in Andøy, Nordland with organisation number 917030847. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 2016. Registered share capital is NOK 1.9m, divided into 1950 shares. The company's stated purpose is: “Drive mottak av fisk som leveres gjennom Bleik havn, og drive pakking, foredling og salg av fiskeprodukter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 346,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 346,000
Equity
NOK 3.2m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns BLEIK FISK AS?

J. M. NILSEN FISK AS
BLEIK FISK AS
NOK 2.7m rev. · NOK 346,000 profit

BLEIK FISK AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BLEIK FISK AS own?

BLEIK FISK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLEIK FISK AS

Who owns BLEIK FISK AS?

J. M. NILSEN FISK AS is the largest registered owner, with 34.0%.

What is the revenue of BLEIK FISK AS?

BLEIK FISK AS had revenue of NOK 2.7m in 2024.

Who is the general manager of BLEIK FISK AS?

Carl Martin Hatlestad is registered as general manager of BLEIK FISK AS.

Where is BLEIK FISK AS based?

BLEIK FISK AS has its business address in Bleik.

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.