BIZTRAC BETA
Activities of excursion and event organisers

ESS EVENT

Org. no. 933108392 Limited company (AS) Lørenskog Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 292,000
Equity NOK 81,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-14 Adresseendring registrert 2026-02-14.

ESS EVENT is registered as a limited company in Lørenskog, Akershus with organisation number 933108392. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg, planlegging og gjennomføring av arrangementer, aktiviteter og opplevelser for bedrifter, privatpersoner, institusjoner, skoler og idrettslag, herunder medieproduksjon, salg av profileringsartikler og relaterte produkter, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 292,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 292,000
Equity
NOK 81,000
Est. value
NOK 1.3m

Financial health · 2025

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

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

Who owns ESS EVENT?

KOLLSTRØM HOLDING AS
ESS EVENT
NOK 6.3m rev. · NOK 292,000 profit

ESS EVENT has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ESS EVENT

Who owns ESS EVENT?

KOLLSTRØM HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of ESS EVENT?

ESS EVENT had revenue of NOK 6.3m in 2025.

Where is ESS EVENT based?

ESS EVENT 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.