BIZTRAC BETA
Rental and operating of own or leased real estate

RØROS KOBBERVERK AS

Org. no. 996467139 Limited company (AS) Røros Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −59,000
Equity NOK 18.7m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−59k kr).

RØROS KOBBERVERK AS is registered as a limited company in Røros, Trøndelag with organisation number 996467139. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Virksomhet innenfor utvikling og investering i andre selskaper og all virksomhet tilknyttet dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −59,000
Equity
NOK 18.7m
Est. value
NOK 15.3m

Financial health · 2024

Liquidity
2.86
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
71.5%
Very good
Equity as a share of total capital

Who owns RØROS KOBBERVERK AS?

PÅL SELBOE VALSETH
RØROS KOBBERVERK AS
NOK 0 rev. · NOK −59,000 profit

RØROS KOBBERVERK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RØROS KOBBERVERK AS own?

RØROS KOBBERVERK AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about RØROS KOBBERVERK AS

Who owns RØROS KOBBERVERK AS?

PÅL SELBOE VALSETH is the largest registered owner, with 100.0%.

What is the revenue of RØROS KOBBERVERK AS?

RØROS KOBBERVERK AS had revenue of NOK 0 in 2024.

Where is RØROS KOBBERVERK AS based?

RØROS KOBBERVERK AS has its business address in Røros.

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.