BIZTRAC BETA
Hairdressing and barber activities

HÅRSPESIALISTEN AS

Org. no. 920273858 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 111,000
Equity NOK 257,000
Incorporated 2018
Share capital NOK 562,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HÅRSPESIALISTEN AS is registered as a limited company in Oslo, Oslo with organisation number 920273858. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2018. Registered share capital is NOK 562,000, divided into 1000 shares. The company's stated purpose is: “Salg av frisørtjenester og frisørprodukter samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 111,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 111,000
Equity
NOK 257,000
Est. value
NOK 582,000

Financial health · 2025

Liquidity
2.65
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
62.3%
Very good
Equity as a share of total capital

Who owns HÅRSPESIALISTEN AS?

STIC AS
HÅRSPESIALISTEN AS
NOK 1.3m rev. · NOK 111,000 profit

HÅRSPESIALISTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HÅRSPESIALISTEN AS

Who owns HÅRSPESIALISTEN AS?

STIC AS is the largest registered owner, with 100.0%.

What is the revenue of HÅRSPESIALISTEN AS?

HÅRSPESIALISTEN AS had revenue of NOK 1.3m in 2025.

Who is the general manager of HÅRSPESIALISTEN AS?

Erik Ruhs is registered as general manager of HÅRSPESIALISTEN AS.

Where is HÅRSPESIALISTEN AS based?

HÅRSPESIALISTEN 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.