BIZTRAC BETA
Other captive investment companies

TOBE HOLDING AS

Org. no. 912518272 Limited company (AS) Drammen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 133,000
Operating profit NOK −50,000
Equity NOK 25.7m
Incorporated 2013
Share capital NOK 30,000

Signals

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

TOBE HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 912518272. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer, samt rådgivningstjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 133,000 in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 133,000
Operating profit
NOK −50,000
Equity
NOK 25.7m
Est. value
NOK 14.1m

Financial health · 2024

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

Who owns TOBE HOLDING AS?

TOM BERGET
TOBE HOLDING AS
NOK 133,000 rev. · NOK −50,000 profit

TOBE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TOBE HOLDING AS own?

TOBE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TOBE HOLDING AS

Who owns TOBE HOLDING AS?

TOM BERGET is the largest registered owner, with 100.0%.

What is the revenue of TOBE HOLDING AS?

TOBE HOLDING AS had revenue of NOK 133,000 in 2024.

Who is the general manager of TOBE HOLDING AS?

Tom Berget is registered as general manager of TOBE HOLDING AS.

Where is TOBE HOLDING AS based?

TOBE HOLDING AS has its business address in Drammen.

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.