BIZTRAC BETA
Sound recording and music publishing activities

MAVO MUSIC AS

Org. no. 932426935 Limited company (AS) Steinkjer Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 62,000
Operating profit NOK 4,000
Equity NOK 29,000
Incorporated 2023
Share capital NOK 30,000

MAVO MUSIC AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 932426935. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utgivelse av musikk og lyd - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 62,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2024

Revenue
NOK 62,000
Operating profit
NOK 4,000
Equity
NOK 29,000
Est. value
NOK 38,000

Financial health · 2024

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

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

Who owns MAVO MUSIC AS?

MAVO HOLDING AS
MAVO MUSIC AS
NOK 62,000 rev. · NOK 4,000 profit

MAVO MUSIC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAVO MUSIC AS

Who owns MAVO MUSIC AS?

MAVO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MAVO MUSIC AS?

MAVO MUSIC AS had revenue of NOK 62,000 in 2024.

Who is the general manager of MAVO MUSIC AS?

Magnus Saugestad Andersen is registered as general manager of MAVO MUSIC AS.

Where is MAVO MUSIC AS based?

MAVO MUSIC AS has its business address in Steinkjer.

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.