BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

MEGO AS

Org. no. 934974972 Limited company (AS) Trondheim Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 32,000
Operating profit NOK −122,000
Equity NOK 13.4m
Incorporated 1983
Share capital NOK 100,000

Signals

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

MEGO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 934974972. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 1983. Registered share capital is NOK 100,000, divided into 20 shares. The company's stated purpose is: “Petroleumsteknologisk konsulentvirksomhet, produktutvikling, industri promosjon og mar- kedsføring av produkter og tjenester og alt som står i forbindelse med dette samt del- tagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 32,000 in revenue and NOK −122,000 in operating profit.

Key figures · 2024

Revenue
NOK 32,000
Operating profit
NOK −122,000
Equity
NOK 13.4m
Est. value
NOK 12.3m

Financial health · 2024

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

Who owns MEGO AS?

MICHAEL GOLAN
MEGO AS
NOK 32,000 rev. · NOK −122,000 profit

MEGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEGO AS

Who owns MEGO AS?

MICHAEL GOLAN is the largest registered owner, with 100.0%.

What is the revenue of MEGO AS?

MEGO AS had revenue of NOK 32,000 in 2024.

Who is the general manager of MEGO AS?

Michael Golan is registered as general manager of MEGO AS.

Where is MEGO AS based?

MEGO AS has its business address in Trondheim.

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.