BIZTRAC BETA
Buying and selling of own real estate

CBA HOLDING AS

Org. no. 921337418 Limited company (AS) Færder Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 225,000
Operating profit NOK 140,000
Equity NOK −63,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−63k kr).

CBA HOLDING AS is registered as a limited company in Færder, Vestfold with organisation number 921337418. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer og andeler, deltakelse i andre selskaper med liknende virksomhet, utleie av konsulentvirksomhet samt investering i fast eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 225,000 in revenue and NOK 140,000 in operating profit.

Key figures · 2025

Revenue
NOK 225,000
Operating profit
NOK 140,000
Equity
NOK −63,000
Est. value
NOK 1.2m

Financial health · 2024

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

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

Who owns CBA HOLDING AS?

TØNSBERG VEKST AS
CBA HOLDING AS
NOK 225,000 rev. · NOK 140,000 profit

CBA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CBA HOLDING AS

Who owns CBA HOLDING AS?

TØNSBERG VEKST AS is the largest registered owner, with 100.0%.

What is the revenue of CBA HOLDING AS?

CBA HOLDING AS had revenue of NOK 225,000 in 2025.

Where is CBA HOLDING AS based?

CBA HOLDING AS has its business address in Nøtterøy.

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.