BIZTRAC BETA
Computing infrastructure, data processing, hosting and related activities

CHIP BIDCO AS

Org. no. 923807748 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −6.0m
Equity NOK 1.2bn
Incorporated 2019
Share capital NOK 240,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6,0 mill kr).

CHIP BIDCO AS is registered as a limited company in Oslo, Oslo with organisation number 923807748. The business is classified under computing infrastructure, data processing, hosting and related activities (NACE 63.100). The company was incorporated in 2019. Registered share capital is NOK 240,000, divided into 30000 shares. The company's stated purpose is: “Å investere i og eie aksjer, finansielle instrumenter og andeler i andre selskaper, samt annen virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −6.0m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −6.0m
Equity
NOK 1.2bn
Est. value
NOK 2.2bn

Financial health · 2024

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.7%
Good
Equity as a share of total capital

Who owns CHIP BIDCO AS?

CHIP MIDCO AS
CHIP BIDCO AS
NOK 0 rev. · NOK −6.0m profit

CHIP BIDCO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHIP BIDCO AS own?

CHIP BIDCO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about CHIP BIDCO AS

Who owns CHIP BIDCO AS?

CHIP MIDCO AS is the largest registered owner, with 100.0%.

What is the revenue of CHIP BIDCO AS?

CHIP BIDCO AS had revenue of NOK 0 in 2024.

Where is CHIP BIDCO AS based?

CHIP BIDCO 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.