BIZTRAC BETA
Other support activities to arts and performing arts

PRO EVENT AS

Org. no. 932243989 Limited company (AS) Skiptvet Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 799,000
Operating profit NOK −36,000
Equity NOK 91,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−36k kr).

PRO EVENT AS is registered as a limited company in Skiptvet, Østfold with organisation number 932243989. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Arrangør av festivaler og fest, samt utleie av event utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 799,000 in revenue and NOK −36,000 in operating profit.

Key figures · 2025

Revenue
NOK 799,000
Operating profit
NOK −36,000
Equity
NOK 91,000
Est. value
NOK 851,000

Financial health · 2025

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

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

Who owns PRO EVENT AS?

LUDVIG ANTHONY ENGEBRETSEN
PRO EVENT AS
NOK 799,000 rev. · NOK −36,000 profit

PRO EVENT AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRO EVENT AS

Who owns PRO EVENT AS?

LUDVIG ANTHONY ENGEBRETSEN is the largest registered owner, with 17.0%.

What is the revenue of PRO EVENT AS?

PRO EVENT AS had revenue of NOK 799,000 in 2025.

Who is the general manager of PRO EVENT AS?

Tommy Lorang Ødegaard is registered as general manager of PRO EVENT AS.

Where is PRO EVENT AS based?

PRO EVENT AS has its business address in Skiptvet.

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.