BIZTRAC BETA
Performing arts activities in music

IDA RØNSHAUGEN AS

Org. no. 915546129 Limited company (AS) Sør-Fron Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −6,000
Equity NOK −274,000
Incorporated 2015
Share capital NOK 48,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−274k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

IDA RØNSHAUGEN AS is registered as a limited company in Sør-Fron, Innlandet with organisation number 915546129. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2015. Registered share capital is NOK 48,000, divided into 100 shares. The company's stated purpose is: “Musikkframførelse, arrangering, komponering, produksjon og andre produkter/tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −6,000
Equity
NOK −274,000

Financial health · 2025

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

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

Who owns IDA RØNSHAUGEN AS?

IDA RØNSHAUGEN BREDEVEIEN
IDA RØNSHAUGEN AS
NOK 3,000 rev. · NOK −6,000 profit

IDA RØNSHAUGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IDA RØNSHAUGEN AS

Who owns IDA RØNSHAUGEN AS?

IDA RØNSHAUGEN BREDEVEIEN is the largest registered owner, with 100.0%.

What is the revenue of IDA RØNSHAUGEN AS?

IDA RØNSHAUGEN AS had revenue of NOK 3,000 in 2025.

Where is IDA RØNSHAUGEN AS based?

IDA RØNSHAUGEN AS has its business address in Sør-Fron.

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.