BIZTRAC BETA
Rental and leasing of other personal and household goods

SILENT DISCO EVENTS AS

Org. no. 928323374 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 143,000
Operating profit NOK 26,000
Equity NOK 148,000
Incorporated 2021
Share capital NOK 75,000

SILENT DISCO EVENTS AS is registered as a limited company in Stavanger, Rogaland with organisation number 928323374. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2021. Registered share capital is NOK 75,000, divided into 3000 shares. The company's stated purpose is: “Leie ut utstyr og hjelpe til med promotering for kulturelle, offentlige og private arrangement i Rogaland.”. The most recent filed accounts, for the 2025 financial year, show NOK 143,000 in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 143,000
Operating profit
NOK 26,000
Equity
NOK 148,000
Est. value
NOK 189,000

Financial health · 2025

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

Who owns SILENT DISCO EVENTS AS?

STURLE BREIVIK
SILENT DISCO EVENTS AS
NOK 143,000 rev. · NOK 26,000 profit

SILENT DISCO EVENTS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SILENT DISCO EVENTS AS

Who owns SILENT DISCO EVENTS AS?

STURLE BREIVIK is the largest registered owner, with 66.7%.

What is the revenue of SILENT DISCO EVENTS AS?

SILENT DISCO EVENTS AS had revenue of NOK 143,000 in 2025.

Who is the general manager of SILENT DISCO EVENTS AS?

Odd Arild Breivik is registered as general manager of SILENT DISCO EVENTS AS.

Where is SILENT DISCO EVENTS AS based?

SILENT DISCO EVENTS AS has its business address in Stavanger.

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.