BIZTRAC BETA
Uoppgitt

TBE HOLDING AS

Org. no. 929022629 Limited company (AS) Alver Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK −69,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−69k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).

TBE HOLDING AS is registered as a limited company in Alver, Vestland with organisation number 929022629. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −29,000
Equity
NOK −69,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-123.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TBE HOLDING AS?

Torstein Birkeland Espenes
TBE HOLDING AS
· NOK −29,000 profit

TBE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TBE HOLDING AS own?

TBE HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TBE HOLDING AS

Who owns TBE HOLDING AS?

Torstein Birkeland Espenes is the largest registered owner, with 100.0%.

Who is the general manager of TBE HOLDING AS?

Torstein Birkeland Espenes is registered as general manager of TBE HOLDING AS.

Where is TBE HOLDING AS based?

TBE 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.