biztrac. BETA
COMPANY REGISTER PROFILE
930454931 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Sound recording and music publishing activities

FRØYA PRODUCTIONS DA

Org. no. 930454931 General partnership with shared liability (DA) Ål Incorporated 2022 Active
Ownership graph ↗
Revenue 2023 NOK 100,000
Operating profit NOK −6,000
Equity NOK 0
Incorporated 2022

Signals

1 flags
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−6k kr).

FRØYA PRODUCTIONS DA is registered as a general partnership with shared liability in Ål, Buskerud with organisation number 930454931. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2022. The company's stated purpose is: “Plateselskap. Selskapets formål er å produsere og distribuere innspillinger av musikk skrevet av kvinnelige komponister. Selskapet har ansvar for produksjon, distribusjon og salg av musikkinnspillinger i digitalt og fysisk formål.”. The most recent filed accounts, for the 2023 financial year, show NOK 100,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2023

Revenue
NOK 100,000
Operating profit
NOK −6,000
Equity
NOK 0

Financial health · 2023

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns FRØYA PRODUCTIONS DA?

No shareholders are registered for FRØYA PRODUCTIONS DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FRØYA PRODUCTIONS DA

What is the revenue of FRØYA PRODUCTIONS DA?

FRØYA PRODUCTIONS DA had revenue of NOK 100,000 in 2023.

Where is FRØYA PRODUCTIONS DA based?

FRØYA PRODUCTIONS DA has its business address in Ål.

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.