BIZTRAC BETA
Computer programming activities

TUNEFACTORY AS

Org. no. 933245020 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK −10,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−10k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

TUNEFACTORY AS is registered as a limited company in Oslo, Oslo with organisation number 933245020. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og drift av digitale plattformer rettet mot musikkbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK −10,000

Financial health · 2025

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

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

Who owns TUNEFACTORY AS?

REIN MELLBYE VAN VLIET
TUNEFACTORY AS
NOK 0 rev. · NOK −8,000 profit

TUNEFACTORY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TUNEFACTORY AS

Who owns TUNEFACTORY AS?

REIN MELLBYE VAN VLIET is the largest registered owner, with 100.0%.

What is the revenue of TUNEFACTORY AS?

TUNEFACTORY AS had revenue of NOK 0 in 2025.

Who is the general manager of TUNEFACTORY AS?

Rein Mellbye Van Vliet is registered as general manager of TUNEFACTORY AS.

Where is TUNEFACTORY AS based?

TUNEFACTORY 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.