BIZTRAC BETA
Computer consultancy and computer facilities management activities

DLTX CLOUD AS

Org. no. 991436685 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −47,000
Equity NOK −4.1m
Incorporated 2007
Share capital NOK 200,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−47k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DLTX CLOUD AS is registered as a limited company in Oslo, Oslo with organisation number 991436685. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2007. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Utvikling av datasenter og teknologisk infrastruktur tilknyttet web3.”.

Key figures · 2024

Operating profit
NOK −47,000
Equity
NOK −4.1m

Financial health · 2024

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

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

Who owns DLTX CLOUD AS?

RISØR SHIPPING HOLDING AS
DLTX CLOUD AS
· NOK −47,000 profit

DLTX CLOUD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DLTX CLOUD AS er morselskap for 2 datterselskaper:

Frequently asked questions about DLTX CLOUD AS

Who owns DLTX CLOUD AS?

RISØR SHIPPING HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of DLTX CLOUD AS?

Thomas Wollmar Neeven Christensen is registered as general manager of DLTX CLOUD AS.

Where is DLTX CLOUD AS based?

DLTX CLOUD 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.