BIZTRAC BETA
Other captive investment companies

CBU HOLDING AS

Org. no. 918975772 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 1.7m
Incorporated 2017
Share capital NOK 31,000

Signals

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

CBU HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 918975772. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 31,000, divided into 31000 shares. The company's stated purpose is: “Investere i aksjer, fond og annen aktiva og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 1.7m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns CBU HOLDING AS?

CHRISTOFFER BUGGE
CBU HOLDING AS
NOK 0 rev. · NOK −2,000 profit

CBU HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CBU HOLDING AS own?

CBU HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about CBU HOLDING AS

Who owns CBU HOLDING AS?

CHRISTOFFER BUGGE is the largest registered owner, with 100.0%.

What is the revenue of CBU HOLDING AS?

CBU HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of CBU HOLDING AS?

Christoffer Bugge is registered as general manager of CBU HOLDING AS.

Where is CBU HOLDING AS based?

CBU HOLDING AS has its business address in Oslo.

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.