BIZTRAC BETA
Warehousing and storage

REN SJØKABELBEREDSKAP AS

Org. no. 913602110 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 28.2m
Operating profit NOK 1.2m
Equity NOK 10.2m
Incorporated 2014
Share capital NOK 1.0m

REN SJØKABELBEREDSKAP AS is registered as a limited company in Bergen, Vestland with organisation number 913602110. The business is classified under warehousing and storage (NACE 52.100). The company was incorporated in 2014. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Drifte lager for reservemateriell, samt å drive annen virksomhet i forbindelse med dette, herunder å delta i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 28.2m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 28.2m
Operating profit
NOK 1.2m
Equity
NOK 10.2m
Est. value
NOK 9.5m

Financial health · 2024

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

Who owns REN SJØKABELBEREDSKAP AS?

REN AS
REN SJØKABELBEREDSKAP AS
NOK 28.2m rev. · NOK 1.2m profit

REN SJØKABELBEREDSKAP AS has 1 registered shareholder:

All shareholders and roles →

Group structure

REN SJØKABELBEREDSKAP AS er morselskap for 7 datterselskaper:

Frequently asked questions about REN SJØKABELBEREDSKAP AS

Who owns REN SJØKABELBEREDSKAP AS?

REN AS is the largest registered owner, with 100.0%.

What is the revenue of REN SJØKABELBEREDSKAP AS?

REN SJØKABELBEREDSKAP AS had revenue of NOK 28.2m in 2024.

Who is the general manager of REN SJØKABELBEREDSKAP AS?

Bjørn Haukanes is registered as general manager of REN SJØKABELBEREDSKAP AS.

Where is REN SJØKABELBEREDSKAP AS based?

REN SJØKABELBEREDSKAP AS has its business address in Bergen.

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.