BIZTRAC BETA
Retail sale of household articles and equipment n.e.c.

DAMSGÅRD EIENDOM AS

Org. no. 989080687 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 305,000
Operating profit NOK −1.7m
Equity NOK 57.0m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

DAMSGÅRD EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 989080687. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, investering i fast eiendom, verdipapirer med mer. ”. The most recent filed accounts, for the 2024 financial year, show NOK 305,000 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 305,000
Operating profit
NOK −1.7m
Equity
NOK 57.0m
Est. value
NOK 33.7m

Financial health · 2024

Liquidity
7.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
90.3%
Very good
Equity as a share of total capital

Who owns DAMSGÅRD EIENDOM AS?

JAN SVERRE RØSSTAD
DAMSGÅRD EIENDOM AS
NOK 305,000 rev. · NOK −1.7m profit

DAMSGÅRD EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does DAMSGÅRD EIENDOM AS own?

DAMSGÅRD EIENDOM AS holds stakes in 12 companies:

See the full ownership structure →

Frequently asked questions about DAMSGÅRD EIENDOM AS

Who owns DAMSGÅRD EIENDOM AS?

JAN SVERRE RØSSTAD is the largest registered owner, with 37.4%.

What is the revenue of DAMSGÅRD EIENDOM AS?

DAMSGÅRD EIENDOM AS had revenue of NOK 305,000 in 2024.

Where is DAMSGÅRD EIENDOM AS based?

DAMSGÅRD EIENDOM 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.