BIZTRAC BETA
Hairdressing and barber activities

VITALBEAUTY AS

Org. no. 984793944 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 675,000
Operating profit NOK −88,000
Equity NOK −24,000
Incorporated 2002
Share capital NOK 150,000

Signals

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

VITALBEAUTY AS is registered as a limited company in Oslo, Oslo with organisation number 984793944. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2002. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Import av safran og nøtter. Frisør og salg av hårpleieprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 675,000 in revenue and NOK −88,000 in operating profit.

Key figures · 2025

Revenue
NOK 675,000
Operating profit
NOK −88,000
Equity
NOK −24,000

Financial health · 2025

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

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

Who owns VITALBEAUTY AS?

FIRAS SALEM HADAD
VITALBEAUTY AS
NOK 675,000 rev. · NOK −88,000 profit

VITALBEAUTY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VITALBEAUTY AS

Who owns VITALBEAUTY AS?

FIRAS SALEM HADAD is the largest registered owner, with 100.0%.

What is the revenue of VITALBEAUTY AS?

VITALBEAUTY AS had revenue of NOK 675,000 in 2025.

Who is the general manager of VITALBEAUTY AS?

Firas Salem Hadad is registered as general manager of VITALBEAUTY AS.

Where is VITALBEAUTY AS based?

VITALBEAUTY 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.