BIZTRAC BETA
Wholesale of fish, crustaceans and molluscs

KJELLSEA AS

Org. no. 989200364 Limited company (AS) Kinn Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 5.9m
Operating profit NOK −4.1m
Equity NOK 5.2m
Incorporated 2005
Share capital NOK 544,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,1 mill kr).

KJELLSEA AS is registered as a limited company in Kinn, Vestland with organisation number 989200364. The business is classified under wholesale of fish, crustaceans and molluscs (NACE 46.322). The company was incorporated in 2005. Registered share capital is NOK 544,000, divided into 1000 shares. The company's stated purpose is: “Handels-, investerings- og konsulentvirksomhet samt å delta i andre virksomheter i samme eller andre bransjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.9m in revenue and NOK −4.1m in operating profit.

Key figures · 2024

Revenue
NOK 5.9m
Operating profit
NOK −4.1m
Equity
NOK 5.2m
Est. value
NOK 4.4m

Financial health · 2024

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.2%
Good
Equity as a share of total capital

Who owns KJELLSEA AS?

KJELL EINAR HAUGEN
KJELLSEA AS
NOK 5.9m rev. · NOK −4.1m profit

KJELLSEA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJELLSEA AS own?

KJELLSEA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KJELLSEA AS

Who owns KJELLSEA AS?

KJELL EINAR HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of KJELLSEA AS?

KJELLSEA AS had revenue of NOK 5.9m in 2024.

Who is the general manager of KJELLSEA AS?

Kjell Einar Haugen is registered as general manager of KJELLSEA AS.

Where is KJELLSEA AS based?

KJELLSEA AS has its business address in Florø.

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.