BIZTRAC BETA
Repair and maintenance of motor vehicles

RM BILPLEIE & BILSALG AS

Org. no. 922224331 Limited company (AS) Fredrikstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 350,000
Equity NOK 463,000
Incorporated 2019
Employees 7
Share capital NOK 50,000

RM BILPLEIE & BILSALG AS is registered as a limited company in Fredrikstad, Østfold with organisation number 922224331. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2019 and has 7 registered employees. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Bilpleie og salg av brukt bil”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 350,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 350,000
Equity
NOK 463,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns RM BILPLEIE & BILSALG AS?

OMER MOHAMMAD ALHASSAN HAMISH
RM BILPLEIE & BILSALG AS
NOK 2.0m rev. · NOK 350,000 profit

RM BILPLEIE & BILSALG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RM BILPLEIE & BILSALG AS

Who owns RM BILPLEIE & BILSALG AS?

OMER MOHAMMAD ALHASSAN HAMISH is the largest registered owner, with 100.0%.

What is the revenue of RM BILPLEIE & BILSALG AS?

RM BILPLEIE & BILSALG AS had revenue of NOK 2.0m in 2024.

Who is the general manager of RM BILPLEIE & BILSALG AS?

Omer Mohammad Alhassan Hamish is registered as general manager of RM BILPLEIE & BILSALG AS.

Where is RM BILPLEIE & BILSALG AS based?

RM BILPLEIE & BILSALG AS has its business address in Fredrikstad.

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.