BIZTRAC BETA
Hairdressing and barber activities

HÅROLOGISALONGEN AS

Org. no. 997801725 Limited company (AS) Sunnfjord Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 60,000
Equity NOK 160,000
Incorporated 2012
Employees 5
Share capital NOK 90,000

HÅROLOGISALONGEN AS is registered as a limited company in Sunnfjord, Vestland with organisation number 997801725. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 90,000, divided into 90 shares. The company's stated purpose is: “Frisørvirksomhet og andre tjenester i naturlig tilknytning til dette. Selskapet kan og ved aksjetegning eller på annen måte investere og eie aksjer i andre selskaper”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 60,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 60,000
Equity
NOK 160,000
Est. value
NOK 310,000

Financial health · 2024

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

Who owns HÅROLOGISALONGEN AS?

BODIL EKROLL HOFF
HÅROLOGISALONGEN AS
NOK 3.3m rev. · NOK 60,000 profit

HÅROLOGISALONGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HÅROLOGISALONGEN AS

Who owns HÅROLOGISALONGEN AS?

BODIL EKROLL HOFF is the largest registered owner, with 50.0%.

What is the revenue of HÅROLOGISALONGEN AS?

HÅROLOGISALONGEN AS had revenue of NOK 3.3m in 2024.

Who is the general manager of HÅROLOGISALONGEN AS?

Bodil Ekroll Hoff is registered as general manager of HÅROLOGISALONGEN AS.

Where is HÅROLOGISALONGEN AS based?

HÅROLOGISALONGEN AS has its business address in Førde.

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.