BIZTRAC BETA
Other cultural education

NORSK MUSIKKSENTER AS

Org. no. 918530851 Limited company (AS) Sarpsborg Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 420,000
Operating profit NOK 96,000
Equity NOK −47,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

NORSK MUSIKKSENTER AS is registered as a limited company in Sarpsborg, Østfold with organisation number 918530851. The business is classified under other cultural education (NACE 85.529). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Undervisning.”. The most recent filed accounts, for the 2024 financial year, show NOK 420,000 in revenue and NOK 96,000 in operating profit.

Key figures · 2024

Revenue
NOK 420,000
Operating profit
NOK 96,000
Equity
NOK −47,000
Est. value
NOK 567,000

Financial health · 2024

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

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

Who owns NORSK MUSIKKSENTER AS?

FINN-CHRISTIAN LINDELØFF
NORSK MUSIKKSENTER AS
NOK 420,000 rev. · NOK 96,000 profit

NORSK MUSIKKSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSK MUSIKKSENTER AS

Who owns NORSK MUSIKKSENTER AS?

FINN-CHRISTIAN LINDELØFF is the largest registered owner, with 100.0%.

What is the revenue of NORSK MUSIKKSENTER AS?

NORSK MUSIKKSENTER AS had revenue of NOK 420,000 in 2024.

Who is the general manager of NORSK MUSIKKSENTER AS?

Finn-Christian Lindeløff is registered as general manager of NORSK MUSIKKSENTER AS.

Where is NORSK MUSIKKSENTER AS based?

NORSK MUSIKKSENTER AS has its business address in Greåker.

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.