BIZTRAC BETA
Performing arts activities in dramatic arts

SHOWBØCK EVENT AS

Org. no. 930100447 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −23,000
Equity NOK 504,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).

SHOWBØCK EVENT AS is registered as a limited company in Oslo, Oslo with organisation number 930100447. The business is classified under performing arts activities in dramatic arts (NACE 90.202). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon av teater/fester/event/konferanse for næringsliv m.m. samt virksomhet som naturlig står i forbindelse med dette, herunder å ta del i andre virksomheter. Investering i aksjer og selskapsandeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −23,000
Equity
NOK 504,000
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns SHOWBØCK EVENT AS?

BØCK HOLDING AS
SHOWBØCK EVENT AS
NOK 1.5m rev. · NOK −23,000 profit

SHOWBØCK EVENT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SHOWBØCK EVENT AS er morselskap for 1 datterselskap:

Frequently asked questions about SHOWBØCK EVENT AS

Who owns SHOWBØCK EVENT AS?

BØCK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SHOWBØCK EVENT AS?

SHOWBØCK EVENT AS had revenue of NOK 1.5m in 2024.

Where is SHOWBØCK EVENT AS based?

SHOWBØCK EVENT AS has its business address in Oslo.

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.