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

RENNESØY KRABBE AS

Org. no. 851200142 Limited company (AS) Stavanger Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 164,000
Operating profit NOK 18,000
Equity NOK 2.2m
Incorporated 1988
Share capital NOK 150,000

RENNESØY KRABBE AS is registered as a limited company in Stavanger, Rogaland with organisation number 851200142. The business is classified under freezing and further processing of fish, crustaceans and molluscs (NACE 10.203). The company was incorporated in 1988. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Produksjon av renset krabbe i skjell, foredle fisk og skalldyr, og annet som faller naturlig inn under dette, samt kjøp og salg.”. The most recent filed accounts, for the 2025 financial year, show NOK 164,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 164,000
Operating profit
NOK 18,000
Equity
NOK 2.2m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns RENNESØY KRABBE AS?

EVY ØSTHUS HELLEVIK
RENNESØY KRABBE AS
NOK 164,000 rev. · NOK 18,000 profit

RENNESØY KRABBE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RENNESØY KRABBE AS

Who owns RENNESØY KRABBE AS?

EVY ØSTHUS HELLEVIK is the largest registered owner, with 45.0%.

What is the revenue of RENNESØY KRABBE AS?

RENNESØY KRABBE AS had revenue of NOK 164,000 in 2025.

Who is the general manager of RENNESØY KRABBE AS?

Kåre Jan Østhus is registered as general manager of RENNESØY KRABBE AS.

Where is RENNESØY KRABBE AS based?

RENNESØY KRABBE AS has its business address in Rennesø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.