BIZTRAC BETA
Repair and maintenance of motor vehicles

TSBR HOLDING AS

Org. no. 923561137 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −59,000
Equity NOK 7.5m
Incorporated 2019
Share capital NOK 150,000

Signals

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

TSBR HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 923561137. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2019. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskap, kjøp og salg av aksjer og andeler samt andre aktiviteter som er naturlige i sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −59,000
Equity
NOK 7.5m
Est. value
NOK 9.9m

Financial health · 2024

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

Who owns TSBR HOLDING AS?

TOR SIGURD BRANSDAL
TSBR HOLDING AS
NOK 0 rev. · NOK −59,000 profit

TSBR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TSBR HOLDING AS own?

TSBR HOLDING AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about TSBR HOLDING AS

Who owns TSBR HOLDING AS?

TOR SIGURD BRANSDAL is the largest registered owner, with 100.0%.

What is the revenue of TSBR HOLDING AS?

TSBR HOLDING AS had revenue of NOK 0 in 2024.

Where is TSBR HOLDING AS based?

TSBR HOLDING AS has its business address in Kristiansand S.

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.