BIZTRAC BETA
Plumbing installation

RØR PÅ RØROS AS

Org. no. 984422431 Limited company (AS) Røros Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK 587,000
Equity NOK 4.2m
Incorporated 2002
Employees 5
Share capital NOK 30,000

RØR PÅ RØROS AS is registered as a limited company in Røros, Trøndelag with organisation number 984422431. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2002 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg av rørleggertjenester og annet som naturlig hører inn under dette, herunder investering i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK 587,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK 587,000
Equity
NOK 4.2m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns RØR PÅ RØROS AS?

KJETIL ØVERBY
RØR PÅ RØROS AS
NOK 9.9m rev. · NOK 587,000 profit

RØR PÅ RØROS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does RØR PÅ RØROS AS own?

RØR PÅ RØROS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RØR PÅ RØROS AS

Who owns RØR PÅ RØROS AS?

KJETIL ØVERBY is the largest registered owner, with 40.0%.

What is the revenue of RØR PÅ RØROS AS?

RØR PÅ RØROS AS had revenue of NOK 9.9m in 2024.

Who is the general manager of RØR PÅ RØROS AS?

Kjetil Øverby is registered as general manager of RØR PÅ RØROS AS.

Where is RØR PÅ RØROS AS based?

RØR PÅ RØROS 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.