biztrac. BETA
COMPANY REGISTER PROFILE
924351365 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Sound recording and music publishing activities

LOUDKIND MUSIC GROUP AS

Org. no. 924351365 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 64,000
Equity NOK 37,000
Incorporated 2019
Share capital NOK 30,000

LOUDKIND MUSIC GROUP AS is registered as a limited company in Oslo, Oslo with organisation number 924351365. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Produksjoner innenfor media, musikkproduksjon, management, konsulentvirksomhet, innenfor disse grener.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 64,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +0 %
Operating profit
NOK 64,000
▲ +0 %
Equity
NOK 37,000
▲ +0 %
Est. value
NOK 169,000

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
35.7%
Very good
Return on total assets
Solidity
20.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LOUDKIND MUSIC GROUP AS?

LOUDKIND MUSIC GROUP AS
NOK 1.1m rev. · NOK 64,000 profit

LOUDKIND MUSIC GROUP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOUDKIND MUSIC GROUP AS

Who owns LOUDKIND MUSIC GROUP AS?

Emran Surizehi is the largest registered owner, with 100.0%.

What is the revenue of LOUDKIND MUSIC GROUP AS?

LOUDKIND MUSIC GROUP AS had revenue of NOK 1.1m in 2025.

Where is LOUDKIND MUSIC GROUP AS based?

LOUDKIND MUSIC GROUP 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.