BIZTRAC BETA
Marine fishing

KALLEVIK FISKERI AS

Org. no. 926538314 Limited company (AS) Karmøy Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 374,000
Operating profit NOK −178,000
Equity NOK 53,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

KALLEVIK FISKERI AS is registered as a limited company in Karmøy, Rogaland with organisation number 926538314. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Fiskeri- og rederivirksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 374,000 in revenue and NOK −178,000 in operating profit.

Key figures · 2024

Revenue
NOK 374,000
Operating profit
NOK −178,000
Equity
NOK 53,000
Est. value
NOK 235,000

Financial health · 2024

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KALLEVIK FISKERI AS?

KALLEVIK SUBSEA AS
KALLEVIK FISKERI AS
NOK 374,000 rev. · NOK −178,000 profit

KALLEVIK FISKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KALLEVIK FISKERI AS

Who owns KALLEVIK FISKERI AS?

KALLEVIK SUBSEA AS is the largest registered owner, with 100.0%.

What is the revenue of KALLEVIK FISKERI AS?

KALLEVIK FISKERI AS had revenue of NOK 374,000 in 2024.

Who is the general manager of KALLEVIK FISKERI AS?

Håkon Kallevik is registered as general manager of KALLEVIK FISKERI AS.

Where is KALLEVIK FISKERI AS based?

KALLEVIK FISKERI AS has its business address in Kopervik.

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.