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

SPERREFISH AS

Org. no. 934212797 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −656,000
Equity NOK 200.9m
Incorporated 2024
Share capital NOK 500,000

Signals

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

SPERREFISH AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 934212797. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 2024. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Eie og forvalte aksjer og eierandeler i andre selskap med økonomisk virksomhet som formål. Selskapet skal dessuten drive handel.”.

Key figures · 2024

Operating profit
NOK −656,000
Equity
NOK 200.9m
Est. value
NOK 323.4m

Financial health · 2024

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

Who owns SPERREFISH AS?

K I INVEST AS
SPERREFISH AS
· NOK −656,000 profit

SPERREFISH AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SPERREFISH AS own?

SPERREFISH AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about SPERREFISH AS

Who owns SPERREFISH AS?

K I INVEST AS is the largest registered owner, with 52.0%.

Who is the general manager of SPERREFISH AS?

Kjetil Peder Sperre is registered as general manager of SPERREFISH AS.

Where is SPERREFISH AS based?

SPERREFISH AS has its business address in Ellingsøy.

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.