BIZTRAC BETA
Activities of excursion and event organisers

EVENTEMENT AS

Org. no. 920142303 Limited company (AS) Tønsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 54,000
Incorporated 2017
Share capital NOK 100,000

Signals

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

EVENTEMENT AS is registered as a limited company in Tønsberg, Vestfold with organisation number 920142303. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Reiselivstjenester, aktivitetsarrangør, innholdsproduksjon og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 54,000
Est. value
NOK 77,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 EVENTEMENT AS?

TALLAK HELLE BJERKHOLT
EVENTEMENT AS
NOK 0 rev. · NOK −5,000 profit

EVENTEMENT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EVENTEMENT AS own?

EVENTEMENT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EVENTEMENT AS

Who owns EVENTEMENT AS?

TALLAK HELLE BJERKHOLT is the largest registered owner, with 100.0%.

What is the revenue of EVENTEMENT AS?

EVENTEMENT AS had revenue of NOK 0 in 2025.

Where is EVENTEMENT AS based?

EVENTEMENT AS has its business address in Tønsberg.

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.