BIZTRAC BETA
Construction of utility projects for electricity and telecommunications at sea

SEAWORKS KABEL AS

Org. no. 916358091 Limited company (AS) Harstad Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 141.7m
Operating profit NOK −5.3m
Equity NOK 98.9m
Incorporated 2015
Share capital NOK 1.2m

Signals

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

SEAWORKS KABEL AS is registered as a limited company in Harstad, Troms with organisation number 916358091. The business is classified under construction of utility projects for electricity and telecommunications at sea (NACE 42.221). The company was incorporated in 2015. Registered share capital is NOK 1.2m, divided into 124400 shares. The company's stated purpose is: “Maritim virksomhet herunder kabellegging.”. The most recent filed accounts, for the 2024 financial year, show NOK 141.7m in revenue and NOK −5.3m in operating profit.

Key figures · 2024

Revenue
NOK 141.7m
Operating profit
NOK −5.3m
Equity
NOK 98.9m
Est. value
NOK 47.5m

Financial health · 2024

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

Who owns SEAWORKS KABEL AS?

SELØY HOLDING AS
SEAWORKS KABEL AS
NOK 141.7m rev. · NOK −5.3m profit

SEAWORKS KABEL AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEAWORKS KABEL AS

Who owns SEAWORKS KABEL AS?

SELØY HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of SEAWORKS KABEL AS?

SEAWORKS KABEL AS had revenue of NOK 141.7m in 2024.

Who is the general manager of SEAWORKS KABEL AS?

Runar Mørch is registered as general manager of SEAWORKS KABEL AS.

Where is SEAWORKS KABEL AS based?

SEAWORKS KABEL AS has its business address in Harstad.

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.