BIZTRAC BETA
Development of building projects

RØROS BYGG AS

Org. no. 881678802 Limited company (AS) Røros Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK −261,000
Equity NOK 4.7m
Incorporated 2000
Share capital NOK 500,000

Signals

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

RØROS BYGG AS is registered as a limited company in Røros, Trøndelag with organisation number 881678802. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2000. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Investering i eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK −261,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK −261,000
Equity
NOK 4.7m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns RØROS BYGG AS?

ERICSON HOLDING AS
RØROS BYGG AS
NOK 3.2m rev. · NOK −261,000 profit

RØROS BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RØROS BYGG AS own?

RØROS BYGG AS holds a stake in 1 company:

See the full ownership structure →

Group structure

RØROS BYGG AS er morselskap for 1 datterselskap:

Frequently asked questions about RØROS BYGG AS

Who owns RØROS BYGG AS?

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

What is the revenue of RØROS BYGG AS?

RØROS BYGG AS had revenue of NOK 3.2m in 2024.

Who is the general manager of RØROS BYGG AS?

Rolf Eric Ericson is registered as general manager of RØROS BYGG AS.

Where is RØROS BYGG AS based?

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