BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

CLIPPER SEAFOOD AS

Org. no. 963289529 Limited company (AS) Stavanger Incorporated 1992 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK 3.5m
Incorporated 1992
Share capital NOK 1.5m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).

CLIPPER SEAFOOD AS is registered as a limited company in Stavanger, Rogaland with organisation number 963289529. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 1992. Registered share capital is NOK 1.5m, divided into 1500 shares. The company's stated purpose is: “Å drive omsetning, eksport og import av alle typer næringsmidler, samt å drive agentur, produkt- utvikling og/eller industritilvirkning av nærings- midler, herunder også ved aksjetegning eller på annen måte delta i andre selskaper med lignende virksomhet. Selskapet har videre som formål å drive konsulent- virksomhet innen ledelse, markedsføring og produktutvikling/teknologi.”.

Key figures · 2024

Operating profit
NOK −22,000
Equity
NOK 3.5m
Est. value
NOK 4.7m

Financial health · 2024

Liquidity
143.84
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 CLIPPER SEAFOOD AS?

LEIV SVEIN EIKJE
CLIPPER SEAFOOD AS
· NOK −22,000 profit

CLIPPER SEAFOOD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CLIPPER SEAFOOD AS

Who owns CLIPPER SEAFOOD AS?

LEIV SVEIN EIKJE is the largest registered owner, with 100.0%.

Who is the general manager of CLIPPER SEAFOOD AS?

Leiv Svein Eikje is registered as general manager of CLIPPER SEAFOOD AS.

Where is CLIPPER SEAFOOD AS based?

CLIPPER SEAFOOD AS has its business address in Stavanger.

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.