BIZTRAC BETA
COMPANY REGISTER PROFILE
990612765 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

TBF HOLDING AS

Org. no. 990612765 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK 87,000
Equity NOK 37.5m
Incorporated 2006
Share capital NOK 105,000

TBF HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 990612765. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2006. Registered share capital is NOK 105,000, divided into 105 shares. The company's stated purpose is: “Investere i andre selskaper og det som står i naturlig forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK 87,000
▲ +141 %
Equity
NOK 37.5m
▼ −3 %
Est. value
NOK 24.8m

Financial health · 2025

Liquidity
218.32
Very good
Current assets ÷ current liabilities
Profitability
6.4%
Satisfactory
Return on total assets
Solidity
99.6%
Very good
Equity as a share of total capital

Who owns TBF HOLDING AS?

TBF HOLDING AS
· NOK 87,000 profit

TBF HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TBF HOLDING AS own?

TBF HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TBF HOLDING AS

Who owns TBF HOLDING AS?

FREDDY MINDOR HAABERG is the largest registered owner, with 100.0%.

Where is TBF HOLDING AS based?

TBF HOLDING AS has its business address in Eidsvåg I Åsane.

Property

Business address Jordalsveien 1, 5105 Eidsvåg I Åsane
Cadastral unit 4601-216/22/0/0

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.