BIZTRAC BETA
Sound recording and music publishing activities

MUSIKKLOFTET AS

Org. no. 962175341 Limited company (AS) Asker Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 465,000
Operating profit NOK −83,000
Equity NOK 156,000
Incorporated 1991
Share capital NOK 30,000

Signals

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

MUSIKKLOFTET AS is registered as a limited company in Asker, Akershus with organisation number 962175341. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 1991. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Innspilling og produksjon av musikk. Salg av lyd og produksjonstjenester, samt all annen virksomhet med økonomisk vinning som formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 465,000 in revenue and NOK −83,000 in operating profit.

Key figures · 2025

Revenue
NOK 465,000
Operating profit
NOK −83,000
Equity
NOK 156,000
Est. value
NOK 856,000

Financial health · 2025

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

Who owns MUSIKKLOFTET AS?

VIDAR LUNDEN
MUSIKKLOFTET AS
NOK 465,000 rev. · NOK −83,000 profit

MUSIKKLOFTET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MUSIKKLOFTET AS

Who owns MUSIKKLOFTET AS?

VIDAR LUNDEN is the largest registered owner, with 100.0%.

What is the revenue of MUSIKKLOFTET AS?

MUSIKKLOFTET AS had revenue of NOK 465,000 in 2025.

Who is the general manager of MUSIKKLOFTET AS?

Vidar Lunden is registered as general manager of MUSIKKLOFTET AS.

Where is MUSIKKLOFTET AS based?

MUSIKKLOFTET AS has its business address in Asker.

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.