BIZTRAC BETA
Rental and operating of own or leased real estate

TBT AS

Org. no. 989191861 Limited company (AS) Haugesund Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 198,000
Operating profit NOK −175,000
Equity NOK 12.3m
Incorporated 2005
Share capital NOK 150,000

Signals

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

TBT AS is registered as a limited company in Haugesund, Rogaland with organisation number 989191861. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 150,000, divided into 1 shares. The company's stated purpose is: “Eie og forvalte verdipapirer og fast eiendom, og drive handel, tjenesteytende virksomhet og produksjon, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 198,000 in revenue and NOK −175,000 in operating profit.

Key figures · 2024

Revenue
NOK 198,000
Operating profit
NOK −175,000
Equity
NOK 12.3m
Est. value
NOK 9.1m

Financial health · 2024

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

Who owns TBT AS?

TØNNES BERNHARD TØNNESEN
TBT AS
NOK 198,000 rev. · NOK −175,000 profit

TBT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TBT AS own?

TBT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TBT AS

Who owns TBT AS?

TØNNES BERNHARD TØNNESEN is the largest registered owner, with 100.0%.

What is the revenue of TBT AS?

TBT AS had revenue of NOK 198,000 in 2024.

Where is TBT AS based?

TBT AS has its business address in Haugesund.

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.