BIZTRAC BETA
Repair and maintenance of motor vehicles

MPS BILSKADE ENSJØ AS

Org. no. 979952937 Limited company (AS) Oslo Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 39.9m
Operating profit NOK 1.9m
Equity NOK 5.0m
Incorporated 1998
Employees 37
Share capital NOK 100,000

MPS BILSKADE ENSJØ AS is registered as a limited company in Oslo, Oslo with organisation number 979952937. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1998 and has 37 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bilopprettingsverksted og alt hva står i forbindelse med dette. Selskapet skal kunne eie aksjer/andeler i andre selskap og også fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 39.9m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 39.9m
Operating profit
NOK 1.9m
Equity
NOK 5.0m
Est. value
NOK 9.6m

Financial health · 2024

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.2%
Good
Equity as a share of total capital

Who owns MPS BILSKADE ENSJØ AS?

MPS BILSKADE AS
MPS BILSKADE ENSJØ AS
NOK 39.9m rev. · NOK 1.9m profit

MPS BILSKADE ENSJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MPS BILSKADE ENSJØ AS

Who owns MPS BILSKADE ENSJØ AS?

MPS BILSKADE AS is the largest registered owner, with 100.0%.

What is the revenue of MPS BILSKADE ENSJØ AS?

MPS BILSKADE ENSJØ AS had revenue of NOK 39.9m in 2024.

Who is the general manager of MPS BILSKADE ENSJØ AS?

René Toft Andersen is registered as general manager of MPS BILSKADE ENSJØ AS.

Where is MPS BILSKADE ENSJØ AS based?

MPS BILSKADE ENSJØ 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 15.06.2026.

Report a problem

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