BIZTRAC BETA
Painting and glazing

MG-MALER AS

Org. no. 929498968 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK −180,000
Equity NOK −256,000
Incorporated 2022
Employees 7
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−256k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−180k kr).

MG-MALER AS is registered as a limited company in Asker, Akershus with organisation number 929498968. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2022 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg og markedsføring av malertjenester, overflatebehandling og tilhørende håndverkstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK −180,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK −180,000
Equity
NOK −256,000

Financial health · 2024

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-31.6%
Weak
Equity as a share of total capital

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

Who owns MG-MALER AS?

DRITON SHERIFI
MG-MALER AS
NOK 3.7m rev. · NOK −180,000 profit

MG-MALER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MG-MALER AS

Who owns MG-MALER AS?

DRITON SHERIFI is the largest registered owner, with 90.0%.

What is the revenue of MG-MALER AS?

MG-MALER AS had revenue of NOK 3.7m in 2024.

Who is the general manager of MG-MALER AS?

Driton Sherifi is registered as general manager of MG-MALER AS.

Where is MG-MALER AS based?

MG-MALER AS has its business address in Borgen.

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.