BIZTRAC BETA
Accounting and bookkeeping

TBH AS

Org. no. 914821495 Limited company (AS) Frogn Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 168,000
Operating profit NOK −455,000
Equity NOK 206.2m
Incorporated 2015
Share capital NOK 1.3m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−455k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TBH AS is registered as a limited company in Frogn, Akershus with organisation number 914821495. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2015. Registered share capital is NOK 1.3m, divided into 13100 shares. The company's stated purpose is: “Investeringsvirksomhet, fortrinnsvis i aksjer og verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 168,000 in revenue and NOK −455,000 in operating profit.

Key figures · 2024

Revenue
NOK 168,000
Operating profit
NOK −455,000
Equity
NOK 206.2m
Est. value
NOK 889.5m

Financial health · 2024

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

Who owns TBH AS?

THOMAS BRENDEN
TBH AS
NOK 168,000 rev. · NOK −455,000 profit

TBH AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TBH AS own?

TBH AS holds stakes in 15 companies:

See the full ownership structure →

Frequently asked questions about TBH AS

Who owns TBH AS?

THOMAS BRENDEN is the largest registered owner, with 95.0%.

What is the revenue of TBH AS?

TBH AS had revenue of NOK 168,000 in 2024.

Who is the general manager of TBH AS?

Thomas Brenden is registered as general manager of TBH AS.

Where is TBH AS based?

TBH AS has its business address in Drøbak.

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.