BIZTRAC BETA
COMPANY REGISTER PROFILE
920203930 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

MKG HOLDING AS

Org. no. 920203930 Limited company (AS) Rana Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 24,000
Operating profit NOK 11,000
Equity NOK −398,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

MKG HOLDING AS is registered as a limited company in Rana, Nordland with organisation number 920203930. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, eie og/eller medvirke i andre selskaper innen samme virksomhet,salg av tekniske konsulenttjenester, samt alt annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 24,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 24,000
Operating profit
NOK 11,000
Equity
NOK −398,000
Est. value
NOK 53,000

Financial health · 2025

Liquidity
5.54
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-676.6%
Weak
Equity as a share of total capital

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

Who owns MKG HOLDING AS?

KNUT GULLESEN
MKG HOLDING AS
NOK 24,000 rev. · NOK 11,000 profit

MKG HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MKG HOLDING AS

Who owns MKG HOLDING AS?

KNUT GULLESEN is the largest registered owner, with 50.0%.

What is the revenue of MKG HOLDING AS?

MKG HOLDING AS had revenue of NOK 24,000 in 2025.

Where is MKG HOLDING AS based?

MKG HOLDING AS has its business address in Mo I Rana.

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.