BIZTRAC BETA
Activities of amusement parks and theme parks

MEGA FUN AS

Org. no. 914248221 Limited company (AS) Lørenskog Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 14.2m
Operating profit NOK −12.9m
Equity NOK 5.6m
Incorporated 2014
Share capital NOK 662,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12,9 mill kr).

MEGA FUN AS is registered as a limited company in Lørenskog, Akershus with organisation number 914248221. The business is classified under activities of amusement parks and theme parks (NACE 93.210). The company was incorporated in 2014. Registered share capital is NOK 662,000, divided into 330800 shares. The company's stated purpose is: “Drift av innendørs leke og aktivitetssenter, samt kafedrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.2m in revenue and NOK −12.9m in operating profit.

Key figures · 2024

Revenue
NOK 14.2m
Operating profit
NOK −12.9m
Equity
NOK 5.6m
Est. value
NOK 16.8m

Financial health · 2024

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

Who owns MEGA FUN AS?

STIG WERNER HANSEN
MEGA FUN AS
NOK 14.2m rev. · NOK −12.9m profit

MEGA FUN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEGA FUN AS own?

MEGA FUN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MEGA FUN AS

Who owns MEGA FUN AS?

STIG WERNER HANSEN is the largest registered owner, with 100.0%.

What is the revenue of MEGA FUN AS?

MEGA FUN AS had revenue of NOK 14.2m in 2024.

Who is the general manager of MEGA FUN AS?

Ståle Emanuel Johansen is registered as general manager of MEGA FUN AS.

Where is MEGA FUN AS based?

MEGA FUN AS has its business address in Lørenskog.

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.