BIZTRAC BETA
Sound recording and music publishing activities

NORSK LYDSTUDIO AS

Org. no. 998161606 Limited company (AS) Drammen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 64,000
Equity NOK −8,000
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−8k kr).

NORSK LYDSTUDIO AS is registered as a limited company in Drammen, Buskerud with organisation number 998161606. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Produksjon og utgivelse av musikk og lydopptak.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 64,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 64,000
Equity
NOK −8,000
Est. value
NOK 593,000

Financial health · 2024

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

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

Who owns NORSK LYDSTUDIO AS?

SVEN JØRAN MICHELSEN
NORSK LYDSTUDIO AS
NOK 3.8m rev. · NOK 64,000 profit

NORSK LYDSTUDIO AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about NORSK LYDSTUDIO AS

Who owns NORSK LYDSTUDIO AS?

SVEN JØRAN MICHELSEN is the largest registered owner, with 60.0%.

What is the revenue of NORSK LYDSTUDIO AS?

NORSK LYDSTUDIO AS had revenue of NOK 3.8m in 2024.

Who is the general manager of NORSK LYDSTUDIO AS?

Peter Michelsen is registered as general manager of NORSK LYDSTUDIO AS.

Where is NORSK LYDSTUDIO AS based?

NORSK LYDSTUDIO AS has its business address in Mjøndalen.

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.