BIZTRAC BETA
Hairdressing and barber activities

RELAX FRISØR AS

Org. no. 913033094 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 93,000
Equity NOK 149,000
Incorporated 2013
Share capital NOK 30,000

RELAX FRISØR AS is registered as a limited company in Bærum, Akershus with organisation number 913033094. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Frisering og salg av hårprodukter og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 93,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 93,000
Equity
NOK 149,000
Est. value
NOK 427,000

Financial health · 2025

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.6%
Satisfactory
Equity as a share of total capital

Who owns RELAX FRISØR AS?

HOOZAN JAMAL YASSIN
RELAX FRISØR AS
NOK 3.8m rev. · NOK 93,000 profit

RELAX FRISØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RELAX FRISØR AS

Who owns RELAX FRISØR AS?

HOOZAN JAMAL YASSIN is the largest registered owner, with 50.0%.

What is the revenue of RELAX FRISØR AS?

RELAX FRISØR AS had revenue of NOK 3.8m in 2025.

Who is the general manager of RELAX FRISØR AS?

Heidi Ness Møller is registered as general manager of RELAX FRISØR AS.

Where is RELAX FRISØR AS based?

RELAX FRISØR AS has its business address in Bekkestua.

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.