BIZTRAC BETA
Wholesale of perfume and cosmetics

HAIRSTORE AS

Org. no. 987093498 Limited company (AS) Larvik Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 15.7m
Operating profit NOK 127,000
Equity NOK 11.0m
Incorporated 2004
Employees 9
Share capital NOK 4.0m

Signals

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

HAIRSTORE AS is registered as a limited company in Larvik, Vestfold with organisation number 987093498. The business is classified under wholesale of perfume and cosmetics (NACE 46.450). The company was incorporated in 2004 and has 9 registered employees. Registered share capital is NOK 4.0m, divided into 1000 shares. The company's stated purpose is: “Grossistvirksomhet innen frisørbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.7m in revenue and NOK 127,000 in operating profit.

Key figures · 2025

Revenue
NOK 15.7m
Operating profit
NOK 127,000
Equity
NOK 11.0m
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns HAIRSTORE AS?

SMITH LARSEN AS
HAIRSTORE AS
NOK 15.7m rev. · NOK 127,000 profit

HAIRSTORE AS has 2 registered shareholders:

All shareholders and roles →

Group structure

HAIRSTORE AS er morselskap for 1 datterselskap:

Frequently asked questions about HAIRSTORE AS

Who owns HAIRSTORE AS?

SMITH LARSEN AS is the largest registered owner, with 91.0%.

What is the revenue of HAIRSTORE AS?

HAIRSTORE AS had revenue of NOK 15.7m in 2025.

Who is the general manager of HAIRSTORE AS?

Jørgen Smith Larsen is registered as general manager of HAIRSTORE AS.

Where is HAIRSTORE AS based?

HAIRSTORE AS has its business address in Larvik.

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.