BIZTRAC BETA
Sound recording and music publishing activities

BLACK RHINO MUSIC AS

Org. no. 915721591 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 210,000
Operating profit NOK 15,000
Equity NOK 212,000
Incorporated 2015
Share capital NOK 30,000

BLACK RHINO MUSIC AS is registered as a limited company in Stavanger, Rogaland with organisation number 915721591. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Artistutvikling, musikkproduksjon, komposisjon, låtskrivning, utgivelse og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 210,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 210,000
Operating profit
NOK 15,000
Equity
NOK 212,000
Est. value
NOK 170,000

Financial health · 2024

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

Who owns BLACK RHINO MUSIC AS?

KRISTOFFER AASEBØ GRUDE
BLACK RHINO MUSIC AS
NOK 210,000 rev. · NOK 15,000 profit

BLACK RHINO MUSIC AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLACK RHINO MUSIC AS own?

BLACK RHINO MUSIC AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BLACK RHINO MUSIC AS

Who owns BLACK RHINO MUSIC AS?

KRISTOFFER AASEBØ GRUDE is the largest registered owner, with 100.0%.

What is the revenue of BLACK RHINO MUSIC AS?

BLACK RHINO MUSIC AS had revenue of NOK 210,000 in 2024.

Where is BLACK RHINO MUSIC AS based?

BLACK RHINO MUSIC AS has its business address in Stavanger.

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.