BIZTRAC BETA
Activities of excursion and event organisers

SYLBRA EVENTS AS

Org. no. 929487958 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 178,000
Operating profit NOK −22,000
Equity NOK −70,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−70k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).

SYLBRA EVENTS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929487958. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med opplevelser, arrangementer og aktiviteter både til sjøs og på land. Selskapet kan eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 178,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 178,000
Operating profit
NOK −22,000
Equity
NOK −70,000

Financial health · 2024

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

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

Who owns SYLBRA EVENTS AS?

SYLBRA INVEST AS
SYLBRA EVENTS AS
NOK 178,000 rev. · NOK −22,000 profit

SYLBRA EVENTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYLBRA EVENTS AS

Who owns SYLBRA EVENTS AS?

SYLBRA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SYLBRA EVENTS AS?

SYLBRA EVENTS AS had revenue of NOK 178,000 in 2024.

Where is SYLBRA EVENTS AS based?

SYLBRA EVENTS AS has its business address in Trondheim.

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.