BIZTRAC BETA
Hairdressing and barber activities

VULKAN FRISØR AS

Org. no. 999531598 Limited company (AS) Hol Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK −175,000
Equity NOK 431,000
Incorporated 2013
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−175k kr).

VULKAN FRISØR AS is registered as a limited company in Hol, Buskerud with organisation number 999531598. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2013 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisørsalong og annen skjønnhetspleie, herunder salg av tjenester og varer av enhver art i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK −175,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK −175,000
Equity
NOK 431,000
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns VULKAN FRISØR AS?

THORUNN MATTHIASDOTTIR
VULKAN FRISØR AS
NOK 3.1m rev. · NOK −175,000 profit

VULKAN FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VULKAN FRISØR AS

Who owns VULKAN FRISØR AS?

THORUNN MATTHIASDOTTIR is the largest registered owner, with 100.0%.

What is the revenue of VULKAN FRISØR AS?

VULKAN FRISØR AS had revenue of NOK 3.1m in 2025.

Who is the general manager of VULKAN FRISØR AS?

Thorunn Matthiasdottir is registered as general manager of VULKAN FRISØR AS.

Where is VULKAN FRISØR AS based?

VULKAN FRISØR AS has its business address in Geilo.

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.