BIZTRAC BETA
Uoppgitt

MEGOGMINEVIKAN HOLDING AS

Org. no. 932611597 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 204,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

MEGOGMINEVIKAN HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932611597. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. 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 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 fortagende.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK 204,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns MEGOGMINEVIKAN HOLDING AS?

JON MARTIN VIKAN
MEGOGMINEVIKAN HOLDING AS
· NOK −5,000 profit

MEGOGMINEVIKAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEGOGMINEVIKAN HOLDING AS own?

MEGOGMINEVIKAN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MEGOGMINEVIKAN HOLDING AS

Who owns MEGOGMINEVIKAN HOLDING AS?

JON MARTIN VIKAN is the largest registered owner, with 100.0%.

Who is the general manager of MEGOGMINEVIKAN HOLDING AS?

Jon Martin Vikan is registered as general manager of MEGOGMINEVIKAN HOLDING AS.

Where is MEGOGMINEVIKAN HOLDING AS based?

MEGOGMINEVIKAN HOLDING AS has its business address in Heimdal.

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.