biztrac. BETA
COMPANY REGISTER PROFILE
925175935 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SPG DAMMENSVIKA HOLDING AS

Org. no. 925175935 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −87,000
Equity NOK 13.2m
Incorporated 2020
Share capital NOK 160,000

Signals

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

SPG DAMMENSVIKA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 925175935. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 160,000, divided into 159600 shares. The company's stated purpose is: “Investering i fast eiendom eller eierandeler i selskaper som direkte eller indirekte eier fast eiendom, verdipapirer samt annen virksomhet i tilknytning til dette.”.

Former names: SPG BOLIG ÅS HOLDING AS

Key figures · 2025

Operating profit
NOK −87,000
▲ +14 %
Equity
NOK 13.2m
▼ −1 %
Est. value
NOK 12.1m

Financial health · 2025

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

Who owns SPG DAMMENSVIKA HOLDING AS?

SPG DAMMENSVIKA HOLDING AS
· NOK −87,000 profit

SPG DAMMENSVIKA HOLDING AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does SPG DAMMENSVIKA HOLDING AS own?

SPG DAMMENSVIKA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SPG DAMMENSVIKA HOLDING AS

Who owns SPG DAMMENSVIKA HOLDING AS?

HOLTEX AS is the largest registered owner, with 18.0%.

Where is SPG DAMMENSVIKA HOLDING AS based?

SPG DAMMENSVIKA HOLDING 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 03.10.2026.

Report a problem

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