BIZTRAC BETA
COMPANY REGISTER PROFILE
923399100 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of fitness centres

BABO HOLDING AS

Org. no. 923399100 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 16.0m
Incorporated 2019
Share capital NOK 2.7m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

BABO HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 923399100. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 2019. Registered share capital is NOK 2.7m, divided into 5459880 shares. The company's stated purpose is: “Erverve og eie aksjer og andeler i andre selskap og annen virksomhet.”.

Key figures · 2025

Operating profit
NOK −17,000
▲ +50 %
Equity
NOK 16.0m
▼ −0 %
Est. value
NOK 20.0m

Financial health · 2025

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

Who owns BABO HOLDING AS?

BABO HOLDING AS has 13 registered shareholders:

All shareholders and roles →

Frequently asked questions about BABO HOLDING AS

Who owns BABO HOLDING AS?

TALI AS is the largest registered owner, with 50.3%.

Where is BABO HOLDING AS based?

BABO HOLDING AS has its business address in Søreidgrend.

Property

Business address Ekerdalen 11G, 5251 Søreidgrend
Cadastral unit 4601-36/68/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

6 companies are registered at this address.

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.