BIZTRAC BETA
Sound recording and music publishing activities

JO BERGER MYHRE AS

Org. no. 934899768 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 249,000
Equity NOK 274,000
Incorporated 2025
Share capital NOK 30,000

JO BERGER MYHRE AS is registered as a limited company in Oslo, Oslo with organisation number 934899768. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen produksjon av musikk, 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 1.1m in revenue and NOK 249,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 249,000
Equity
NOK 274,000
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns JO BERGER MYHRE AS?

JO BERGER MYHRE
JO BERGER MYHRE AS
NOK 1.1m rev. · NOK 249,000 profit

JO BERGER MYHRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JO BERGER MYHRE AS

Who owns JO BERGER MYHRE AS?

JO BERGER MYHRE is the largest registered owner, with 100.0%.

What is the revenue of JO BERGER MYHRE AS?

JO BERGER MYHRE AS had revenue of NOK 1.1m in 2025.

Who is the general manager of JO BERGER MYHRE AS?

Jo Berger Myhre is registered as general manager of JO BERGER MYHRE AS.

Where is JO BERGER MYHRE AS based?

JO BERGER MYHRE 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.