BIZTRAC BETA
Activities of adventure companies

DYNAMIC EVENTS AS

Org. no. 880415182 Limited company (AS) Asker Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 4,000
Equity NOK 49,000
Incorporated 1998
Share capital NOK 100,000

DYNAMIC EVENTS AS is registered as a limited company in Asker, Akershus with organisation number 880415182. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 1998. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Aktiviteter og utflukter, arrangementer for firmaer og privatpersoner, samt hva hermed står i forbindelse, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 4,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 4,000
Equity
NOK 49,000
Est. value
NOK 42,000

Financial health · 2024

Liquidity
0.77
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.1%
Weak
Equity as a share of total capital

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

Who owns DYNAMIC EVENTS AS?

JOHN ROGER MÖLLERSTRÖM
DYNAMIC EVENTS AS
NOK 1.2m rev. · NOK 4,000 profit

DYNAMIC EVENTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYNAMIC EVENTS AS

Who owns DYNAMIC EVENTS AS?

JOHN ROGER MÖLLERSTRÖM is the largest registered owner, with 100.0%.

What is the revenue of DYNAMIC EVENTS AS?

DYNAMIC EVENTS AS had revenue of NOK 1.2m in 2024.

Who is the general manager of DYNAMIC EVENTS AS?

John Roger Möllerström is registered as general manager of DYNAMIC EVENTS AS.

Where is DYNAMIC EVENTS AS based?

DYNAMIC EVENTS AS has its business address in Asker.

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.