BIZTRAC BETA
Uoppgitt

RØRCO INVEST AS

Org. no. 920207782 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK −163,000
Incorporated 2017
Share capital NOK 90,000

Signals

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

RØRCO INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 920207782. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 90,000, divided into 300000 shares. The company's stated purpose is: “Eie aksjer i Arna & Åsane Rørleggerservice AS og andre selskaper, samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −163,000

Financial health · 2024

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

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

Who owns RØRCO INVEST AS?

BASSE INVEST AS
RØRCO INVEST AS
NOK 0 rev. · NOK −11,000 profit

RØRCO INVEST AS has 12 registered shareholders:

All shareholders and roles →

Which companies does RØRCO INVEST AS own?

RØRCO INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RØRCO INVEST AS

Who owns RØRCO INVEST AS?

BASSE INVEST AS is the largest registered owner, with 29.5%.

What is the revenue of RØRCO INVEST AS?

RØRCO INVEST AS had revenue of NOK 0 in 2024.

Where is RØRCO INVEST AS based?

RØRCO INVEST AS has its business address in Espeland.

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.