BIZTRAC BETA
Other support activities to arts and performing arts

EVENTCREW AS

Org. no. 920915280 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.7m
Operating profit NOK 193,000
Equity NOK 673,000
Incorporated 2018
Employees 97
Share capital NOK 30,000

EVENTCREW AS is registered as a limited company in Oslo, Oslo with organisation number 920915280. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2018 and has 97 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med supplering av bemanning til rigg av underholdningsarrangementer og andre produkter som naturlig faller sammen med dette samt å eie fast eiendom, verdipapirer og andre fordringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 193,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
Operating profit
NOK 193,000
Equity
NOK 673,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns EVENTCREW AS?

RICHARD JOHN PEREIRA DE FREITAS
EVENTCREW AS
NOK 5.7m rev. · NOK 193,000 profit

EVENTCREW AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EVENTCREW AS

Who owns EVENTCREW AS?

RICHARD JOHN PEREIRA DE FREITAS is the largest registered owner, with 45.0%.

What is the revenue of EVENTCREW AS?

EVENTCREW AS had revenue of NOK 5.7m in 2025.

Who is the general manager of EVENTCREW AS?

Peter Panagiotis Høie is registered as general manager of EVENTCREW AS.

Where is EVENTCREW AS based?

EVENTCREW AS has its business address in Oslo.

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.