BIZTRAC BETA
Sound recording and music publishing activities

MEAU AS

Org. no. 932916754 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 654,000
Operating profit NOK −7,000
Equity NOK 41,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

MEAU AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932916754. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2024. 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 2025 financial year, show NOK 654,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 654,000
Operating profit
NOK −7,000
Equity
NOK 41,000
Est. value
NOK 584,000

Financial health · 2025

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

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

Who owns MEAU AS?

JØRGEN MEYER
MEAU AS
NOK 654,000 rev. · NOK −7,000 profit

MEAU AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEAU AS

Who owns MEAU AS?

JØRGEN MEYER is the largest registered owner, with 100.0%.

What is the revenue of MEAU AS?

MEAU AS had revenue of NOK 654,000 in 2025.

Who is the general manager of MEAU AS?

Jørgen Meyer is registered as general manager of MEAU AS.

Where is MEAU AS based?

MEAU AS has its business address in Trondheim.

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.