BIZTRAC BETA
Rental and operating of own or leased real estate

RAUMA TWEED EIENDOM AS

Org. no. 998234565 Limited company (AS) Røros Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 1.0m
Equity NOK 8.6m
Incorporated 2012
Share capital NOK 371,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RAUMA TWEED EIENDOM AS is registered as a limited company in Røros, Trøndelag with organisation number 998234565. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 371,000, divided into 500 shares. The company's stated purpose is: “Utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 1.0m
Equity
NOK 8.6m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns RAUMA TWEED EIENDOM AS?

RAUMA HOLDING AS
RAUMA TWEED EIENDOM AS
NOK 1.4m rev. · NOK 1.0m profit

RAUMA TWEED EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RAUMA TWEED EIENDOM AS

Who owns RAUMA TWEED EIENDOM AS?

RAUMA HOLDING AS is the largest registered owner, with 90.2%.

What is the revenue of RAUMA TWEED EIENDOM AS?

RAUMA TWEED EIENDOM AS had revenue of NOK 1.4m in 2024.

Who is the general manager of RAUMA TWEED EIENDOM AS?

Arnstein Digernes is registered as general manager of RAUMA TWEED EIENDOM AS.

Where is RAUMA TWEED EIENDOM AS based?

RAUMA TWEED 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.