BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

PACO MUSIC AS

Org. no. 998740649 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 813,000
Equity NOK 8.6m
Incorporated 2012
Share capital NOK 50,000

PACO MUSIC AS is registered as a limited company in Trondheim, Trøndelag with organisation number 998740649. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Booking og management for artister samt det som naturlig står i forbindelse med dette, herunder å være arrangør av konserter, festivaler m.m. Eie og leie ut hytte(r) til komponister, forfattere og de som naturlig faller inn under dette. Være rådgiver for aktører som driver med virksomhet dekket av denne paragraf.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 813,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 813,000
Equity
NOK 8.6m
Est. value
NOK 8.3m

Financial health · 2025

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

Who owns PACO MUSIC AS?

STEIN ROSANOFF VANEBO
PACO MUSIC AS
NOK 1.2m rev. · NOK 813,000 profit

PACO MUSIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PACO MUSIC AS

Who owns PACO MUSIC AS?

STEIN ROSANOFF VANEBO is the largest registered owner, with 100.0%.

What is the revenue of PACO MUSIC AS?

PACO MUSIC AS had revenue of NOK 1.2m in 2025.

Where is PACO MUSIC AS based?

PACO MUSIC AS has its business address in Trondheim.

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.