BIZTRAC BETA
Sound recording and music publishing activities

FR SANG OG MUSIKK AS

Org. no. 932525372 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 480,000
Operating profit NOK −13,000
Equity NOK −24,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−24k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).

FR SANG OG MUSIKK AS is registered as a limited company in Stavanger, Rogaland with organisation number 932525372. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 60000 shares. The company's stated purpose is: “Musikkproduksjon- og fremføring, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 480,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 480,000
Operating profit
NOK −13,000
Equity
NOK −24,000

Financial health · 2024

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

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

Who owns FR SANG OG MUSIKK AS?

LESTOLE AS
FR SANG OG MUSIKK AS
NOK 480,000 rev. · NOK −13,000 profit

FR SANG OG MUSIKK AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about FR SANG OG MUSIKK AS

Who owns FR SANG OG MUSIKK AS?

LESTOLE AS is the largest registered owner, with 16.7%.

What is the revenue of FR SANG OG MUSIKK AS?

FR SANG OG MUSIKK AS had revenue of NOK 480,000 in 2024.

Where is FR SANG OG MUSIKK AS based?

FR SANG OG MUSIKK AS has its business address in Stavanger.

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.