biztrac. BETA
COMPANY REGISTER PROFILE
927611260 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
General cleaning of buildings

MG HOLDNING AS

Org. no. 927611260 Limited company (AS) Oslo Incorporated 2021 Active
Operating profit NOK −10,000
Equity NOK −13,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−13k kr).

MG HOLDNING AS is registered as a limited company in Oslo, Oslo with organisation number 927611260. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −10,000
▲ +60 %
Equity
NOK −13,000
▼ −462 %

Financial health · 2024

Liquidity
23.14
Very good
Current assets ÷ current liabilities
Profitability
2.0%
Weak
Return on total assets
Solidity
-4.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns MG HOLDNING AS?

MG HOLDNING AS
· NOK −10,000 profit

MG HOLDNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MG HOLDNING AS own?

MG HOLDNING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MG HOLDNING AS

Who owns MG HOLDNING AS?

Vimal Yathavarajar is the largest registered owner, with 100.0%.

Who is the general manager of MG HOLDNING AS?

Saumiyan Thayaparan is registered as general manager of MG HOLDNING AS.

Where is MG HOLDNING AS based?

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