BIZTRAC BETA
Performing arts activities in music

BØLGEN ENTERTAINMENT AS

Org. no. 925913685 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 590,000
Operating profit NOK 151,000
Equity NOK 515,000
Incorporated 2020
Share capital NOK 30,000

BØLGEN ENTERTAINMENT AS is registered as a limited company in Drammen, Buskerud with organisation number 925913685. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon, utgivelse, formidling av musikk, foredrag samt salg av artikler relatert til artistvirksomheten.”. The most recent filed accounts, for the 2025 financial year, show NOK 590,000 in revenue and NOK 151,000 in operating profit.

Key figures · 2025

Revenue
NOK 590,000
Operating profit
NOK 151,000
Equity
NOK 515,000
Est. value
NOK 838,000

Financial health · 2025

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

Who owns BØLGEN ENTERTAINMENT AS?

NIKLAS WILLIAM PAULSEN
BØLGEN ENTERTAINMENT AS
NOK 590,000 rev. · NOK 151,000 profit

BØLGEN ENTERTAINMENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BØLGEN ENTERTAINMENT AS

Who owns BØLGEN ENTERTAINMENT AS?

NIKLAS WILLIAM PAULSEN is the largest registered owner, with 100.0%.

What is the revenue of BØLGEN ENTERTAINMENT AS?

BØLGEN ENTERTAINMENT AS had revenue of NOK 590,000 in 2025.

Who is the general manager of BØLGEN ENTERTAINMENT AS?

Julian William Paulsen is registered as general manager of BØLGEN ENTERTAINMENT AS.

Where is BØLGEN ENTERTAINMENT AS based?

BØLGEN ENTERTAINMENT AS has its business address in Drammen.

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.