biztrac. BETA
COMPANY REGISTER PROFILE
998783909 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of electrical equipment

RMT BUSINESS & FINANCE AS

Org. no. 998783909 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 115,000
Equity NOK 366,000
Incorporated 2012
Share capital NOK 30,000

RMT BUSINESS & FINANCE AS is registered as a limited company in Oslo, Oslo with organisation number 998783909. The business is classified under repair and maintenance of electrical equipment (NACE 33.140). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Reparasjon og service på motiltelefoner, datamaskiner og annen forbrukerelektronikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 115,000 in operating profit.

Former names: OSLO MOBIL OG PC SERVICE AS

Key figures · 2025

Revenue
NOK 1.2m
▲ +0 %
Operating profit
NOK 115,000
▼ −15 %
Equity
NOK 366,000
▲ +45 %
Est. value
NOK 767,000

Financial health · 2025

Liquidity
-0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
591.3%
Very good
Equity as a share of total capital

Who owns RMT BUSINESS & FINANCE AS?

RMT BUSINESS & FINANCE AS
NOK 1.2m rev. · NOK 115,000 profit

RMT BUSINESS & FINANCE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RMT BUSINESS & FINANCE AS

Who owns RMT BUSINESS & FINANCE AS?

Issam Mohamed Salih is the largest registered owner, with 100.0%.

What is the revenue of RMT BUSINESS & FINANCE AS?

RMT BUSINESS & FINANCE AS had revenue of NOK 1.2m in 2025.

Where is RMT BUSINESS & FINANCE AS based?

RMT BUSINESS & FINANCE AS has its business address in Oslo.

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.