BIZTRAC BETA
Performing arts activities in music

TURBO ARTIST AS

Org. no. 986774556 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −452,000
Equity NOK 458,000
Incorporated 2004
Share capital NOK 120,000

Signals

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

TURBO ARTIST AS is registered as a limited company in Oslo, Oslo with organisation number 986774556. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2004. Registered share capital is NOK 120,000, divided into 120 shares. The company's stated purpose is: “Drive virksomhet med innspilling og fremføring av musikk samt utvikling av artistkarrierer og alt som naturlig hører til dette, samt delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −452,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −452,000
Equity
NOK 458,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
4.59
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
78.2%
Very good
Equity as a share of total capital

Who owns TURBO ARTIST AS?

TURBO ARTIST AS
TURBO ARTIST AS
NOK 1.1m rev. · NOK −452,000 profit

TURBO ARTIST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does TURBO ARTIST AS own?

TURBO ARTIST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TURBO ARTIST AS

Who owns TURBO ARTIST AS?

TURBO ARTIST AS is the largest registered owner, with 40.0%.

What is the revenue of TURBO ARTIST AS?

TURBO ARTIST AS had revenue of NOK 1.1m in 2024.

Where is TURBO ARTIST AS based?

TURBO ARTIST AS has its business address in Oslo.

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.