biztrac. BETA
COMPANY REGISTER PROFILE
924358459 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

RMJ 5 AS

Org. no. 924358459 Limited company (AS) Skien Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 708,000
Operating profit NOK 283,000
Equity NOK 235,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

RMJ 5 AS is registered as a limited company in Skien, Telemark with organisation number 924358459. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytnig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 708,000 in revenue and NOK 283,000 in operating profit.

Key figures · 2025

Revenue
NOK 708,000
▲ +0 %
Operating profit
NOK 283,000
▲ +3 %
Equity
NOK 235,000
▲ +121 %
Est. value
NOK 644,000

Financial health · 2025

Liquidity
2.68
Very good
Current assets ÷ current liabilities
Profitability
2.9%
Weak
Return on total assets
Solidity
2.4%
Not satisfactory
Equity as a share of total capital

Who owns RMJ 5 AS?

RMJ 5 AS
NOK 708,000 rev. · NOK 283,000 profit

RMJ 5 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RMJ 5 AS

Who owns RMJ 5 AS?

SALVARE AS is the largest registered owner, with 100.0%.

What is the revenue of RMJ 5 AS?

RMJ 5 AS had revenue of NOK 708,000 in 2025.

Where is RMJ 5 AS based?

RMJ 5 AS has its business address in Skien.

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

Report a problem

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