BIZTRAC BETA
COMPANY REGISTER PROFILE
918835547 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

DS CAPITAL AS

Org. no. 918835547 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 218,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

DS CAPITAL AS is registered as a limited company in Oslo, Oslo with organisation number 918835547. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsaktiviteter og rådgivning, og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK 218,000
Est. value
NOK 199,000

Financial health · 2025

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

Who owns DS CAPITAL AS?

DANIEL SØRHEIM
DS CAPITAL AS
· NOK −5,000 profit

DS CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DS CAPITAL AS own?

DS CAPITAL AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about DS CAPITAL AS

Who owns DS CAPITAL AS?

DANIEL SØRHEIM is the largest registered owner, with 100.0%.

Who is the general manager of DS CAPITAL AS?

Daniel Sørheim is registered as general manager of DS CAPITAL AS.

Where is DS CAPITAL AS based?

DS CAPITAL 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.