BIZTRAC BETA
Marine fishing

KABELFISK AS

Org. no. 923568042 Limited company (AS) Lebesby Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −58,000
Equity NOK −128,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−128k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−58k kr).

KABELFISK AS is registered as a limited company in Lebesby, Finnmark with organisation number 923568042. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive fiske etter Torsk, Sei, Hyse,kongekrabbe og andre fiskeslag på Finnmarkskysten. Delta i virksomheter med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −58,000
Equity
NOK −128,000

Financial health · 2024

Liquidity
0.60
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.3%
Weak
Equity as a share of total capital

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

Who owns KABELFISK AS?

Kim Abel Pedersen
KABELFISK AS
NOK 1.0m rev. · NOK −58,000 profit

KABELFISK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KABELFISK AS

Who owns KABELFISK AS?

Kim Abel Pedersen is the largest registered owner, with 100.0%.

What is the revenue of KABELFISK AS?

KABELFISK AS had revenue of NOK 1.0m in 2024.

Who is the general manager of KABELFISK AS?

Kim Abel Pedersen is registered as general manager of KABELFISK AS.

Where is KABELFISK AS based?

KABELFISK AS has its business address in Kjøllefjord.

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.