BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

STAVERN SKALLDYR AS

Org. no. 925777447 Limited company (AS) Larvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 1.2m
Equity NOK 121,000
Incorporated 2020
Share capital NOK 40,000

STAVERN SKALLDYR AS is registered as a limited company in Larvik, Vestfold with organisation number 925777447. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2020. Registered share capital is NOK 40,000, divided into 400 shares. The company's stated purpose is: “Engros- og detaljhandelvirksomhet innen næringsmiddelbransjen, herunder kjøp og salg av fisk og skalldyr, samt alt som står i forbindelse med dette, herunder deltagelse i selskapet med liknende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 1.2m
Equity
NOK 121,000
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.5%
Weak
Equity as a share of total capital

Who owns STAVERN SKALLDYR AS?

GEIR UNO DRENG
STAVERN SKALLDYR AS
NOK 6.8m rev. · NOK 1.2m profit

STAVERN SKALLDYR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STAVERN SKALLDYR AS

Who owns STAVERN SKALLDYR AS?

GEIR UNO DRENG is the largest registered owner, with 50.0%.

What is the revenue of STAVERN SKALLDYR AS?

STAVERN SKALLDYR AS had revenue of NOK 6.8m in 2024.

Who is the general manager of STAVERN SKALLDYR AS?

Anders Paulsen is registered as general manager of STAVERN SKALLDYR AS.

Where is STAVERN SKALLDYR AS based?

STAVERN SKALLDYR AS has its business address in Stavern.

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.