BIZTRAC BETA
Sound recording and music publishing activities

MAKE MUSIC PUBLISHING AS

Org. no. 995927845 Limited company (AS) Nordre Follo Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 113,000
Operating profit NOK 8,000
Equity NOK 222,000
Incorporated 2010
Share capital NOK 100,000

MAKE MUSIC PUBLISHING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 995927845. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Fremstilling/salg av rettigheter til musikk og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 113,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 113,000
Operating profit
NOK 8,000
Equity
NOK 222,000
Est. value
NOK 169,000

Financial health · 2024

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

Who owns MAKE MUSIC PUBLISHING AS?

MAKE MUSIC AS
MAKE MUSIC PUBLISHING AS
NOK 113,000 rev. · NOK 8,000 profit

MAKE MUSIC PUBLISHING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MAKE MUSIC PUBLISHING AS

Who owns MAKE MUSIC PUBLISHING AS?

MAKE MUSIC AS is the largest registered owner, with 90.0%.

What is the revenue of MAKE MUSIC PUBLISHING AS?

MAKE MUSIC PUBLISHING AS had revenue of NOK 113,000 in 2024.

Where is MAKE MUSIC PUBLISHING AS based?

MAKE MUSIC PUBLISHING AS has its business address in Oppegård.

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.