BIZTRAC BETA
Performing arts activities in music

STUDIO RABBEN AS

Org. no. 927211521 Limited company (AS) Lyngen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 784,000
Operating profit NOK −14,000
Equity NOK 52,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).

STUDIO RABBEN AS is registered as a limited company in Lyngen, Troms with organisation number 927211521. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arrangere musikk og andre kulturarrangement. Utleie arbeidskraft. Lydproduksjon, deltagelse i andre selskap. Entrepenørvirksomhets samt beslektede virksomheter. Evenement og turistservice.”. The most recent filed accounts, for the 2024 financial year, show NOK 784,000 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 784,000
Operating profit
NOK −14,000
Equity
NOK 52,000
Est. value
NOK 818,000

Financial health · 2024

Liquidity
1.88
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.4%
Weak
Equity as a share of total capital

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

Who owns STUDIO RABBEN AS?

GUSTAV HARRY LINDQUIST
STUDIO RABBEN AS
NOK 784,000 rev. · NOK −14,000 profit

STUDIO RABBEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STUDIO RABBEN AS

Who owns STUDIO RABBEN AS?

GUSTAV HARRY LINDQUIST is the largest registered owner, with 90.0%.

What is the revenue of STUDIO RABBEN AS?

STUDIO RABBEN AS had revenue of NOK 784,000 in 2024.

Where is STUDIO RABBEN AS based?

STUDIO RABBEN AS has its business address in Nord-Lenangen.

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.