BIZTRAC BETA
Sports and recreation education

MEGIMOVE AS

Org. no. 932486962 Limited company (AS) Lindesnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 55,000
Operating profit NOK −3,000
Equity NOK 5,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

MEGIMOVE AS is registered as a limited company in Lindesnes, Agder with organisation number 932486962. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å tilby personlig trening, kurs og undervisning, produksjon av video og foto, reklame- og markedsføringstjenester, samt investering og egenkapitalforvaltning/trading.”. The most recent filed accounts, for the 2024 financial year, show NOK 55,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 55,000
Operating profit
NOK −3,000
Equity
NOK 5,000
Est. value
NOK 51,000

Financial health · 2024

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

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

Who owns MEGIMOVE AS?

MERGIM NEZIRAJ
MEGIMOVE AS
NOK 55,000 rev. · NOK −3,000 profit

MEGIMOVE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEGIMOVE AS own?

MEGIMOVE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MEGIMOVE AS

Who owns MEGIMOVE AS?

MERGIM NEZIRAJ is the largest registered owner, with 100.0%.

What is the revenue of MEGIMOVE AS?

MEGIMOVE AS had revenue of NOK 55,000 in 2024.

Where is MEGIMOVE AS based?

MEGIMOVE AS has its business address in Mandal.

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.