BIZTRAC BETA
Other support activities to arts and performing arts

TINNITUS PRODUCTION AS

Org. no. 998525454 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 214,000
Equity NOK 478,000
Incorporated 2012
Share capital NOK 30,000

TINNITUS PRODUCTION AS is registered as a limited company in Oslo, Oslo with organisation number 998525454. The business is classified under other support activities to arts and performing arts (NACE 90.390). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å produsere musikk og tilby lydtekniske tjenester live og i studio, i tillegg vil en andel av virksomheten tilby tjenester innenfor grafisk design.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 214,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 214,000
Equity
NOK 478,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns TINNITUS PRODUCTION AS?

ESPEN HØYDALSVIK
TINNITUS PRODUCTION AS
NOK 1.1m rev. · NOK 214,000 profit

TINNITUS PRODUCTION AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TINNITUS PRODUCTION AS own?

TINNITUS PRODUCTION AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TINNITUS PRODUCTION AS

Who owns TINNITUS PRODUCTION AS?

ESPEN HØYDALSVIK is the largest registered owner, with 100.0%.

What is the revenue of TINNITUS PRODUCTION AS?

TINNITUS PRODUCTION AS had revenue of NOK 1.1m in 2024.

Where is TINNITUS PRODUCTION AS based?

TINNITUS PRODUCTION 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.