BIZTRAC BETA
Other captive investment companies

TBB HOLDING AS

Org. no. 989233327 Limited company (AS) Alver Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 4.6m
Incorporated 2005
Share capital NOK 100,000

Signals

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

TBB HOLDING AS is registered as a limited company in Alver, Vestland with organisation number 989233327. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 4.6m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns TBB HOLDING AS?

BJØRN RUNE BLOMVÅGNES
TBB HOLDING AS
NOK 0 rev. · NOK −16,000 profit

TBB HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TBB HOLDING AS own?

TBB HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TBB HOLDING AS

Who owns TBB HOLDING AS?

BJØRN RUNE BLOMVÅGNES is the largest registered owner, with 50.0%.

What is the revenue of TBB HOLDING AS?

TBB HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of TBB HOLDING AS?

Bjørn Rune Blomvågnes is registered as general manager of TBB HOLDING AS.

Where is TBB HOLDING AS based?

TBB HOLDING AS has its business address in Isdalstø.

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.