BIZTRAC BETA
Manufacture of other electronic and electric wires and cables

NORCABLE AS

Org. no. 918400567 Limited company (AS) Karmøy Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 104.8m
Operating profit NOK 7.6m
Equity NOK 17.1m
Incorporated 2017
Employees 43
Share capital NOK 161,000

NORCABLE AS is registered as a limited company in Karmøy, Rogaland with organisation number 918400567. The business is classified under manufacture of other electronic and electric wires and cables (NACE 27.320). The company was incorporated in 2017 and has 43 registered employees. Registered share capital is NOK 161,000, divided into 161276 shares. The company's stated purpose is: “Produsere kraftkabler samt hva hermed står i forbindelse, herunder å delta i andre foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 104.8m in revenue and NOK 7.6m in operating profit.

Key figures · 2024

Revenue
NOK 104.8m
Operating profit
NOK 7.6m
Equity
NOK 17.1m
Est. value
NOK 34.5m

Financial health · 2024

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.8%
Good
Equity as a share of total capital

Who owns NORCABLE AS?

VALINOR AS
NORCABLE AS
NOK 104.8m rev. · NOK 7.6m profit

NORCABLE AS has 7 registered shareholders:

All shareholders and roles →

Which companies does NORCABLE AS own?

NORCABLE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORCABLE AS

Who owns NORCABLE AS?

VALINOR AS is the largest registered owner, with 32.3%.

What is the revenue of NORCABLE AS?

NORCABLE AS had revenue of NOK 104.8m in 2024.

Who is the general manager of NORCABLE AS?

Bengt Haugland is registered as general manager of NORCABLE AS.

Where is NORCABLE AS based?

NORCABLE AS has its business address in Håvik.

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.