BIZTRAC BETA
Sound recording and music publishing activities

VRANG PRODUKSJON AS

Org. no. 918198032 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 18.9m
Operating profit NOK 9.0m
Equity NOK 25.3m
Incorporated 2016
Employees 5
Share capital NOK 30,000

VRANG PRODUKSJON AS is registered as a limited company in Oslo, Oslo with organisation number 918198032. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2016 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjonsselskap for innhold til radio og andre medieplattformer, samt utleie av arbeidskraft, investering i eiendom og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.9m in revenue and NOK 9.0m in operating profit.

Key figures · 2024

Revenue
NOK 18.9m
Operating profit
NOK 9.0m
Equity
NOK 25.3m
Est. value
NOK 46.6m

Financial health · 2024

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

Who owns VRANG PRODUKSJON AS?

CHRISTINE DANCKE
VRANG PRODUKSJON AS
NOK 18.9m rev. · NOK 9.0m profit

VRANG PRODUKSJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VRANG PRODUKSJON AS

Who owns VRANG PRODUKSJON AS?

CHRISTINE DANCKE is the largest registered owner, with 100.0%.

What is the revenue of VRANG PRODUKSJON AS?

VRANG PRODUKSJON AS had revenue of NOK 18.9m in 2024.

Who is the general manager of VRANG PRODUKSJON AS?

Christine Dancke is registered as general manager of VRANG PRODUKSJON AS.

Where is VRANG PRODUKSJON AS based?

VRANG PRODUKSJON 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.