BIZTRAC BETA
Uoppgitt

CDNIL 888 HOLDING AS

Org. no. 932821591 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 3.9m
Incorporated 2023
Share capital NOK 30,000

Signals

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

CDNIL 888 HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 932821591. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Erverve og eie aksjer og andeler i andre selskaper, handel i finansielle instrumenter samt all annen virksomhet som naturlig hører derved.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 3.9m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns CDNIL 888 HOLDING AS?

CHRISTOFFER DAHLSTRØM NILSEN
CDNIL 888 HOLDING AS
NOK 0 rev. · NOK −9,000 profit

CDNIL 888 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CDNIL 888 HOLDING AS own?

CDNIL 888 HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CDNIL 888 HOLDING AS

Who owns CDNIL 888 HOLDING AS?

CHRISTOFFER DAHLSTRØM NILSEN is the largest registered owner, with 100.0%.

What is the revenue of CDNIL 888 HOLDING AS?

CDNIL 888 HOLDING AS had revenue of NOK 0 in 2025.

Where is CDNIL 888 HOLDING AS based?

CDNIL 888 HOLDING AS has its business address in Ålesund.

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.