BIZTRAC BETA
Hairdressing and barber activities

Luggen Hårstudio AS

Org. no. 942399243 Limited company (AS) Molde Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 26.0m
Operating profit NOK 1.2m
Equity NOK 1.9m
Incorporated 1987
Employees 36
Share capital NOK 100,000

Luggen Hårstudio AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 942399243. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1987 and has 36 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Salg og markedsføring av frisørtjenester og produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.0m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 26.0m
Operating profit
NOK 1.2m
Equity
NOK 1.9m
Est. value
NOK 5.5m

Financial health · 2024

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

Who owns Luggen Hårstudio AS?

BLOND AS
Luggen Hårstudio AS
NOK 26.0m rev. · NOK 1.2m profit

Luggen Hårstudio AS has 1 registered shareholder:

All shareholders and roles →

Which companies does Luggen Hårstudio AS own?

Luggen Hårstudio AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about Luggen Hårstudio AS

Who owns Luggen Hårstudio AS?

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

What is the revenue of Luggen Hårstudio AS?

Luggen Hårstudio AS had revenue of NOK 26.0m in 2024.

Who is the general manager of Luggen Hårstudio AS?

Jannicke Lyngstad Mordal is registered as general manager of Luggen Hårstudio AS.

Where is Luggen Hårstudio AS based?

Luggen Hårstudio AS has its business address in Molde.

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.