BIZTRAC BETA
Performing arts activities in music

MUSIKK & SPRÅK AS

Org. no. 927984474 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 668,000
Operating profit NOK 123,000
Equity NOK 19,000
Incorporated 2021
Share capital NOK 30,000

MUSIKK & SPRÅK AS is registered as a limited company in Oslo, Oslo with organisation number 927984474. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utøvelse av musikk inklusiv kursvirksomhet, språkundervisning, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 668,000 in revenue and NOK 123,000 in operating profit.

Key figures · 2025

Revenue
NOK 668,000
Operating profit
NOK 123,000
Equity
NOK 19,000
Est. value
NOK 530,000

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.5%
Weak
Equity as a share of total capital

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

Who owns MUSIKK & SPRÅK AS?

SAFAA JABBAR HASSAN AL-SAADI
MUSIKK & SPRÅK AS
NOK 668,000 rev. · NOK 123,000 profit

MUSIKK & SPRÅK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MUSIKK & SPRÅK AS

Who owns MUSIKK & SPRÅK AS?

SAFAA JABBAR HASSAN AL-SAADI is the largest registered owner, with 50.0%.

What is the revenue of MUSIKK & SPRÅK AS?

MUSIKK & SPRÅK AS had revenue of NOK 668,000 in 2025.

Who is the general manager of MUSIKK & SPRÅK AS?

Abeer Haider Kadhim Al-Mahdawi is registered as general manager of MUSIKK & SPRÅK AS.

Where is MUSIKK & SPRÅK AS based?

MUSIKK & SPRÅK 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.