BIZTRAC BETA
Activities of excursion and event organisers

BAYER STREET EVENT AS

Org. no. 827945382 Limited company (AS) Sandefjord Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 194,000
Equity NOK 755,000
Incorporated 2021
Share capital NOK 30,000

BAYER STREET EVENT AS is registered as a limited company in Sandefjord, Vestfold with organisation number 827945382. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Skape møteplasser for næringslivet og gjennom gode opplevelser bidra til å styrke bedriftenes relasjoner til kunder, leverandører og ansatte.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 194,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
Operating profit
NOK 194,000
Equity
NOK 755,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns BAYER STREET EVENT AS?

JAN ROGER HENRIKSEN
BAYER STREET EVENT AS
NOK 6.0m rev. · NOK 194,000 profit

BAYER STREET EVENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BAYER STREET EVENT AS

Who owns BAYER STREET EVENT AS?

JAN ROGER HENRIKSEN is the largest registered owner, with 100.0%.

What is the revenue of BAYER STREET EVENT AS?

BAYER STREET EVENT AS had revenue of NOK 6.0m in 2025.

Who is the general manager of BAYER STREET EVENT AS?

Jan Roger Henriksen is registered as general manager of BAYER STREET EVENT AS.

Where is BAYER STREET EVENT AS based?

BAYER STREET EVENT AS has its business address in Sandefjord.

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.