BIZTRAC BETA
Performing arts activities in music

TIGERSTATE MUSIC AS

Org. no. 929169964 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 371,000
Operating profit NOK 13,000
Equity NOK −14,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−14k kr).

TIGERSTATE MUSIC AS is registered as a limited company in Oslo, Oslo with organisation number 929169964. The business is classified under performing arts activities in music (NACE 90.201). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med kreativ musikalsk virksomhet, herunder fremføringer, låtskriving og utgivelse av musikkverk, samt rettigheter og inntekter fra slike virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 371,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2024

Revenue
NOK 371,000
Operating profit
NOK 13,000
Equity
NOK −14,000
Est. value
NOK 116,000

Financial health · 2024

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

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

Who owns TIGERSTATE MUSIC AS?

ELIAS ØSTREM TAFJORD
TIGERSTATE MUSIC AS
NOK 371,000 rev. · NOK 13,000 profit

TIGERSTATE MUSIC AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TIGERSTATE MUSIC AS

Who owns TIGERSTATE MUSIC AS?

ELIAS ØSTREM TAFJORD is the largest registered owner, with 33.3%.

What is the revenue of TIGERSTATE MUSIC AS?

TIGERSTATE MUSIC AS had revenue of NOK 371,000 in 2024.

Where is TIGERSTATE MUSIC AS based?

TIGERSTATE MUSIC 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.