BIZTRAC BETA
Civil engineering activities

RØROS OPPMÅLING AS

Org. no. 833170392 Limited company (AS) Røros Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 44,000
Operating profit NOK −16,000
Equity NOK 40,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

RØROS OPPMÅLING AS is registered as a limited company in Røros, Trøndelag with organisation number 833170392. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen byggteknisk konsulentvirksomhet - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 44,000 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 44,000
Operating profit
NOK −16,000
Equity
NOK 40,000
Est. value
NOK 66,000

Financial health · 2025

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

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

Who owns RØROS OPPMÅLING AS?

TROSTEN CONSULT AS
RØROS OPPMÅLING AS
NOK 44,000 rev. · NOK −16,000 profit

RØROS OPPMÅLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØROS OPPMÅLING AS

Who owns RØROS OPPMÅLING AS?

TROSTEN CONSULT AS is the largest registered owner, with 100.0%.

What is the revenue of RØROS OPPMÅLING AS?

RØROS OPPMÅLING AS had revenue of NOK 44,000 in 2025.

Where is RØROS OPPMÅLING AS based?

RØROS OPPMÅLING AS has its business address in Brekkebygd.

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.