BIZTRAC BETA
Hairdressing and barber activities

D AMOUR AS

Org. no. 933065472 Limited company (AS) Halden Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 839,000
Operating profit NOK 5,000
Equity NOK −123,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−123k kr).

D AMOUR AS is registered as a limited company in Halden, Østfold with organisation number 933065472. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen skjønnhetspleie - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 839,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 839,000
Operating profit
NOK 5,000
Equity
NOK −123,000
Est. value
NOK 22,000

Financial health · 2025

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-66.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns D AMOUR AS?

MARIJA SIPRAK
D AMOUR AS
NOK 839,000 rev. · NOK 5,000 profit

D AMOUR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about D AMOUR AS

Who owns D AMOUR AS?

MARIJA SIPRAK is the largest registered owner, with 50.0%.

What is the revenue of D AMOUR AS?

D AMOUR AS had revenue of NOK 839,000 in 2025.

Who is the general manager of D AMOUR AS?

Marija Siprak is registered as general manager of D AMOUR AS.

Where is D AMOUR AS based?

D AMOUR AS has its business address in Tistedal.

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.