biztrac. BETA
COMPANY REGISTER PROFILE
916100884 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠MUSIKKVERDEN AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Retail sale of cultural and recreational goods n.e.c.

MUSIKKVERDEN AS

Org. no. 916100884 Limited company (AS) Tromsø Incorporated 2015 In liquidation
Revenue 2025 NOK 4.2m
Operating profit NOK −443,000
Equity NOK 225,000
Incorporated 2015
Share capital NOK 450,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

MUSIKKVERDEN AS is registered as a limited company in Tromsø, Troms with organisation number 916100884. The business is classified under retail sale of cultural and recreational goods n.e.c. (NACE 47.690). The company was incorporated in 2015. Registered share capital is NOK 450,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av instrumenter, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.2m in revenue and NOK −443,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.2m
▼ −33 %
Operating profit
NOK −443,000
▼ −46 %
Equity
NOK 225,000
▼ −69 %

Financial health · 2025

Liquidity
19.54
Very good
Current assets ÷ current liabilities
Profitability
-21.9%
Not satisfactory
Return on total assets
Solidity
16.1%
Satisfactory
Equity as a share of total capital

Who owns MUSIKKVERDEN AS?

MUSIKKVERDEN AS
NOK 4.2m rev. · NOK −443,000 profit

MUSIKKVERDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MUSIKKVERDEN AS

Who owns MUSIKKVERDEN AS?

Stine Wilsgård is the largest registered owner, with 100.0%.

What is the revenue of MUSIKKVERDEN AS?

MUSIKKVERDEN AS had revenue of NOK 4.2m in 2025.

Where is MUSIKKVERDEN AS based?

MUSIKKVERDEN AS has its business address in Tromsø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.