BIZTRAC BETA
Buying and selling of own real estate

DSP HOLDING AS

Org. no. 816496292 Limited company (AS) Klepp Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 519,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

DSP HOLDING AS is registered as a limited company in Klepp, Rogaland with organisation number 816496292. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper, samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 519,000
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns DSP HOLDING AS?

DAG STIAN POLLESTAD
DSP HOLDING AS
NOK 0 rev. · NOK −10,000 profit

DSP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DSP HOLDING AS own?

DSP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DSP HOLDING AS

Who owns DSP HOLDING AS?

DAG STIAN POLLESTAD is the largest registered owner, with 100.0%.

What is the revenue of DSP HOLDING AS?

DSP HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of DSP HOLDING AS?

Dag Stian Pollestad is registered as general manager of DSP HOLDING AS.

Where is DSP HOLDING AS based?

DSP HOLDING AS has its business address in Kleppe.

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.