BIZTRAC BETA
Wholesale of other household goods

MUSIKKLOSEN AS

Org. no. 977066085 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 755,000
Operating profit NOK −437,000
Equity NOK 3.0m
Incorporated 1997
Share capital NOK 150,000

Signals

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

MUSIKKLOSEN AS is registered as a limited company in Oslo, Oslo with organisation number 977066085. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 1997. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Import av CD plater og andre produkter som naturlig faller sammen med dette for distribusjon/ salg til norske platebutikker og tilsvarende distribusjon av plater fra norske selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 755,000 in revenue and NOK −437,000 in operating profit.

Key figures · 2025

Revenue
NOK 755,000
Operating profit
NOK −437,000
Equity
NOK 3.0m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns MUSIKKLOSEN AS?

ODD GJELSNES
MUSIKKLOSEN AS
NOK 755,000 rev. · NOK −437,000 profit

MUSIKKLOSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MUSIKKLOSEN AS

Who owns MUSIKKLOSEN AS?

ODD GJELSNES is the largest registered owner, with 93.3%.

What is the revenue of MUSIKKLOSEN AS?

MUSIKKLOSEN AS had revenue of NOK 755,000 in 2025.

Who is the general manager of MUSIKKLOSEN AS?

Odd Gjelsnes is registered as general manager of MUSIKKLOSEN AS.

Where is MUSIKKLOSEN AS based?

MUSIKKLOSEN 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.