BIZTRAC BETA
Sound recording and music publishing activities

WOLFGANG WEE PRODUCTIONS AS

Org. no. 930905879 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 1.9m
Equity NOK 354,000
Incorporated 2023
Share capital NOK 30,000

WOLFGANG WEE PRODUCTIONS AS is registered as a limited company in Bærum, Akershus with organisation number 930905879. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produsere og publisere podkaster, videoer og musikkproduksjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 1.9m
Equity
NOK 354,000
Est. value
NOK 6.2m

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.6%
Satisfactory
Equity as a share of total capital

Who owns WOLFGANG WEE PRODUCTIONS AS?

WOLFGANG WEE HOLDING AS
WOLFGANG WEE PRODUCTIONS AS
NOK 3.6m rev. · NOK 1.9m profit

WOLFGANG WEE PRODUCTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WOLFGANG WEE PRODUCTIONS AS

Who owns WOLFGANG WEE PRODUCTIONS AS?

WOLFGANG WEE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of WOLFGANG WEE PRODUCTIONS AS?

WOLFGANG WEE PRODUCTIONS AS had revenue of NOK 3.6m in 2025.

Who is the general manager of WOLFGANG WEE PRODUCTIONS AS?

Wolfgang Wee is registered as general manager of WOLFGANG WEE PRODUCTIONS AS.

Where is WOLFGANG WEE PRODUCTIONS AS based?

WOLFGANG WEE PRODUCTIONS AS has its business address in Fornebu.

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.