BIZTRAC BETA
Retail sale of motor vehicles

MG SERVICE AS

Org. no. 984305168 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 454,000
Operating profit NOK −9,000
Equity NOK 1.8m
Incorporated 2002
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

MG SERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 984305168. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2002. Registered share capital is NOK 200,000, divided into 1200 shares. The company's stated purpose is: “Import og salg av brukte biler, import og omsetning av nye og brukte bildeler og datautstysr med service på samme, kjøp og salg av konkursbo og handelsvarer, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 454,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 454,000
Operating profit
NOK −9,000
Equity
NOK 1.8m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns MG SERVICE AS?

KJELL HAGEN NILSEN
MG SERVICE AS
NOK 454,000 rev. · NOK −9,000 profit

MG SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MG SERVICE AS

Who owns MG SERVICE AS?

KJELL HAGEN NILSEN is the largest registered owner, with 100.0%.

What is the revenue of MG SERVICE AS?

MG SERVICE AS had revenue of NOK 454,000 in 2024.

Who is the general manager of MG SERVICE AS?

Kjell Hagen Nilsen is registered as general manager of MG SERVICE AS.

Where is MG SERVICE AS based?

MG SERVICE 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.