BIZTRAC BETA
COMPANY REGISTER PROFILE
913362101 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

RØROS EIENDOM AS

Org. no. 913362101 Limited company (AS) Stjørdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 790,000
Operating profit NOK 732,000
Equity NOK −1.8m
Incorporated 2014
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,8 mill kr).

RØROS EIENDOM AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 913362101. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 790,000 in revenue and NOK 732,000 in operating profit.

Key figures · 2025

Revenue
NOK 790,000
▼ −17 %
Operating profit
NOK 732,000
▲ +297 %
Equity
NOK −1.8m
▲ +22 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
23.47
Very good
Current assets ÷ current liabilities
Profitability
9.8%
Satisfactory
Return on total assets
Solidity
-28.8%
Weak
Equity as a share of total capital

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

Who owns RØROS EIENDOM AS?

RØROS EIENDOM AS
NOK 790,000 rev. · NOK 732,000 profit

RØROS EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØROS EIENDOM AS

Who owns RØROS EIENDOM AS?

KVISLABAKKEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of RØROS EIENDOM AS?

RØROS EIENDOM AS had revenue of NOK 790,000 in 2025.

Where is RØROS EIENDOM AS based?

RØROS EIENDOM AS has its business address in Stjørdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.