BIZTRAC BETA
Rental and operating of own or leased real estate

R-METALL EIENDOM AS

Org. no. 925881198 Limited company (AS) Råde Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 292,000
Operating profit NOK −703,000
Equity NOK 2.3m
Incorporated 2020
Share capital NOK 30,000

Signals

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

R-METALL EIENDOM AS is registered as a limited company in Råde, Østfold with organisation number 925881198. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom samt annen virksomhet som står i naturlig sammenheng med dette, salg av varer og tjenester, kjøp og salg av aksjer samt medvirke i andre selskaper, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 292,000 in revenue and NOK −703,000 in operating profit.

Key figures · 2024

Revenue
NOK 292,000
Operating profit
NOK −703,000
Equity
NOK 2.3m
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.1%
Weak
Equity as a share of total capital

Who owns R-METALL EIENDOM AS?

R.M. HOLDING AS
R-METALL EIENDOM AS
NOK 292,000 rev. · NOK −703,000 profit

R-METALL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R-METALL EIENDOM AS

Who owns R-METALL EIENDOM AS?

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

What is the revenue of R-METALL EIENDOM AS?

R-METALL EIENDOM AS had revenue of NOK 292,000 in 2024.

Where is R-METALL EIENDOM AS based?

R-METALL EIENDOM AS has its business address in Råde.

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.