BIZTRAC BETA
Rental and operating of own or leased real estate

RØROS PRODUKTER EIENDOM AS

Org. no. 930078603 Limited company (AS) Røros Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 1.8m
Equity NOK 1.8m
Incorporated 2022
Share capital NOK 55,000

RØROS PRODUKTER EIENDOM AS is registered as a limited company in Røros, Trøndelag with organisation number 930078603. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 55,000, divided into 5500 shares. The company's stated purpose is: “Å eie fast eiendom eller aksjer i selskaper som eier fast eiendom, utvikle, omsette, leie ut og for øvrig administrere fast eiendom, samt hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 1.8m
Equity
NOK 1.8m
Est. value
NOK 4.6m

Financial health · 2025

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

Who owns RØROS PRODUKTER EIENDOM AS?

KVARTS HOLDING AS
RØROS PRODUKTER EIENDOM AS
NOK 2.8m rev. · NOK 1.8m profit

RØROS PRODUKTER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RØROS PRODUKTER EIENDOM AS er morselskap for 3 datterselskaper:

Frequently asked questions about RØROS PRODUKTER EIENDOM AS

Who owns RØROS PRODUKTER EIENDOM AS?

KVARTS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RØROS PRODUKTER EIENDOM AS?

RØROS PRODUKTER EIENDOM AS had revenue of NOK 2.8m in 2025.

Where is RØROS PRODUKTER EIENDOM AS based?

RØROS PRODUKTER EIENDOM 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.