BIZTRAC BETA
Hairdressing and barber activities

MELINA HÅR & VELVÆRE AS

Org. no. 929663985 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 635,000
Operating profit NOK −4,000
Equity NOK −148,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−148k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

MELINA HÅR & VELVÆRE AS is registered as a limited company in Drammen, Buskerud with organisation number 929663985. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Frisørsalong, klipper, former, farger og endrer strukturen til ulike typer hår.”. The most recent filed accounts, for the 2025 financial year, show NOK 635,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 635,000
Operating profit
NOK −4,000
Equity
NOK −148,000

Financial health · 2025

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

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

Who owns MELINA HÅR & VELVÆRE AS?

NARGES NAZARI
MELINA HÅR & VELVÆRE AS
NOK 635,000 rev. · NOK −4,000 profit

MELINA HÅR & VELVÆRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MELINA HÅR & VELVÆRE AS

Who owns MELINA HÅR & VELVÆRE AS?

NARGES NAZARI is the largest registered owner, with 100.0%.

What is the revenue of MELINA HÅR & VELVÆRE AS?

MELINA HÅR & VELVÆRE AS had revenue of NOK 635,000 in 2025.

Where is MELINA HÅR & VELVÆRE AS based?

MELINA HÅR & VELVÆRE AS has its business address in Drammen.

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.