BIZTRAC BETA
Hairdressing and barber activities

HEAD FRISØR SANDEFJORD AS

Org. no. 930353205 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 540,000
Equity NOK 214,000
Incorporated 2022
Employees 9
Share capital NOK 30,000

HEAD FRISØR SANDEFJORD AS is registered as a limited company in Oslo, Oslo with organisation number 930353205. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Frisørtjenester, salg av varer tilknyttet frisørvirksomhet, og det som naturlig henger sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 540,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 540,000
Equity
NOK 214,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns HEAD FRISØR SANDEFJORD AS?

TOR DANIEL BERGE
HEAD FRISØR SANDEFJORD AS
NOK 4.8m rev. · NOK 540,000 profit

HEAD FRISØR SANDEFJORD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEAD FRISØR SANDEFJORD AS

Who owns HEAD FRISØR SANDEFJORD AS?

TOR DANIEL BERGE is the largest registered owner, with 100.0%.

What is the revenue of HEAD FRISØR SANDEFJORD AS?

HEAD FRISØR SANDEFJORD AS had revenue of NOK 4.8m in 2025.

Who is the general manager of HEAD FRISØR SANDEFJORD AS?

Tor Daniel Berge is registered as general manager of HEAD FRISØR SANDEFJORD AS.

Where is HEAD FRISØR SANDEFJORD AS based?

HEAD FRISØR SANDEFJORD 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.