BIZTRAC BETA
Repair and maintenance of motor vehicles

MPS BILSKADE FORNEBU AS

Org. no. 924393459 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 12.1m
Operating profit NOK 964,000
Equity NOK 888,000
Incorporated 2019
Employees 11
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.

MPS BILSKADE FORNEBU AS is registered as a limited company in Bærum, Akershus with organisation number 924393459. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2019 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av bilopprettings- og lakkeringsverksted samt tjenester som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.1m in revenue and NOK 964,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.1m
Operating profit
NOK 964,000
Equity
NOK 888,000
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns MPS BILSKADE FORNEBU AS?

MPS BILSKADE AS
MPS BILSKADE FORNEBU AS
NOK 12.1m rev. · NOK 964,000 profit

MPS BILSKADE FORNEBU AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MPS BILSKADE FORNEBU AS

Who owns MPS BILSKADE FORNEBU AS?

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

What is the revenue of MPS BILSKADE FORNEBU AS?

MPS BILSKADE FORNEBU AS had revenue of NOK 12.1m in 2024.

Where is MPS BILSKADE FORNEBU AS based?

MPS BILSKADE FORNEBU AS has its business address in Fornebu.

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.