BIZTRAC BETA
Sound recording and music publishing activities

TBC RECORDS AS

Org. no. 921215444 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 586,000
Operating profit NOK −12,000
Equity NOK −199,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

TBC RECORDS AS is registered as a limited company in Bærum, Akershus with organisation number 921215444. 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 30000 shares. The company's stated purpose is: “Investering i, og forvaltning av, eierskap i selskaper innen musikkforlegging samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 586,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 586,000
Operating profit
NOK −12,000
Equity
NOK −199,000

Financial health · 2025

Liquidity
2.14
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-37.0%
Weak
Equity as a share of total capital

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

Who owns TBC RECORDS AS?

SVALBARD UNITED AS
TBC RECORDS AS
NOK 586,000 rev. · NOK −12,000 profit

TBC RECORDS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TBC RECORDS AS

Who owns TBC RECORDS AS?

SVALBARD UNITED AS is the largest registered owner, with 66.7%.

What is the revenue of TBC RECORDS AS?

TBC RECORDS AS had revenue of NOK 586,000 in 2025.

Where is TBC RECORDS AS based?

TBC RECORDS AS has its business address in Sandvika.

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.