biztrac. BETA
COMPANY REGISTER PROFILE
933925463 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other software publishing

DATASTEEL TOPCO AS

Org. no. 933925463 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −933,000
Equity NOK 925.3m
Incorporated 2024
Share capital NOK 80,000

Signals

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

DATASTEEL TOPCO AS is registered as a limited company in Bærum, Akershus with organisation number 933925463. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2024. Registered share capital is NOK 80,000, divided into 80156573 shares. The company's stated purpose is: “Å investere i og/eller eie aksjer, finansielle instrumenter og andeler i andre selskaper, både ved egenkapital og gjeld, samt annen virksomhet som står i naturlig forbindelse med dette.”.

Former names: NFH 2406165 AS

Key figures · 2025

Operating profit
NOK −933,000
▼ −392 %
Equity
NOK 925.3m
▲ +0 %
Est. value
NOK 1.7bn

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
98.8%
Very good
Equity as a share of total capital

Who owns DATASTEEL TOPCO AS?

CORTEN CAPITAL II LP GB
KVARTERSBOLAGET 2 I LJUSDAL AB SE
RICHARD WATERHOUSE GB
BISTRA PAPAZOVA BG
DATASTEEL TOPCO AS
· NOK −933,000 profit

DATASTEEL TOPCO AS has 7 registered shareholders:

All shareholders and roles →

Which companies does DATASTEEL TOPCO AS own?

DATASTEEL TOPCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DATASTEEL TOPCO AS

Who owns DATASTEEL TOPCO AS?

CORTEN CAPITAL II LP is the largest registered owner, with 81.2%.

Where is DATASTEEL TOPCO AS based?

DATASTEEL TOPCO AS has its business address in Lysaker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.