BIZTRAC BETA
Sound recording and music publishing activities

STUDIOBOX AS

Org. no. 921270666 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 11,000
Operating profit NOK −12,000
Equity NOK −25,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

STUDIOBOX AS is registered as a limited company in Tromsø, Troms with organisation number 921270666. The business is classified under sound recording and music publishing activities (NACE 59.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikle samt produsere og selge lyd-programmer.”. The most recent filed accounts, for the 2024 financial year, show NOK 11,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 11,000
Operating profit
NOK −12,000
Equity
NOK −25,000

Financial health · 2024

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

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

Who owns STUDIOBOX AS?

Bjørn Ole Lindseth
STUDIOBOX AS
NOK 11,000 rev. · NOK −12,000 profit

STUDIOBOX AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STUDIOBOX AS

Who owns STUDIOBOX AS?

Bjørn Ole Lindseth is the largest registered owner, with 100.0%.

What is the revenue of STUDIOBOX AS?

STUDIOBOX AS had revenue of NOK 11,000 in 2024.

Who is the general manager of STUDIOBOX AS?

Bjørn Ole Lindseth is registered as general manager of STUDIOBOX AS.

Where is STUDIOBOX AS based?

STUDIOBOX AS has its business address in Tromsdalen.

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.