biztrac. BETA
COMPANY REGISTER PROFILE
928200981 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

ROYAL HAIR AS

Org. no. 928200981 Limited company (AS) Lillestrøm Incorporated 2021 Active
Revenue 2025 NOK 2.1m
Operating profit NOK −188,000
Equity NOK 315,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

ROYAL HAIR AS is registered as a limited company in Lillestrøm, Akershus with organisation number 928200981. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg og montering av Hair Extension produkter for hår pleie, hårpleie, Klipp/pleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK −188,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
▲ +40 %
Operating profit
NOK −188,000
▼ −144 %
Equity
NOK 315,000
▼ −38 %
Est. value
NOK 405,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
-30.0%
Not satisfactory
Return on total assets
Solidity
54.4%
Very good
Equity as a share of total capital

Who owns ROYAL HAIR AS?

ROYAL HAIR AS
NOK 2.1m rev. · NOK −188,000 profit

ROYAL HAIR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROYAL HAIR AS

Who owns ROYAL HAIR AS?

Ali Reza Jorshery is the largest registered owner, with 100.0%.

What is the revenue of ROYAL HAIR AS?

ROYAL HAIR AS had revenue of NOK 2.1m in 2025.

Who is the general manager of ROYAL HAIR AS?

Kamilla Natali Jorshery is registered as general manager of ROYAL HAIR AS.

Where is ROYAL HAIR AS based?

ROYAL HAIR AS has its business address in Lillestrøm.

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.