BIZTRAC BETA
Hairdressing and barber activities

CUT HÅR OG VELVÆRE AS

Org. no. 919948825 Limited company (AS) Stad Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 470,000
Equity NOK 576,000
Incorporated 2017
Share capital NOK 70,000

Signals

1 flags
  • Nylig endring 2026-05-23 Aksjekapital registrert 2026-05-23.

CUT HÅR OG VELVÆRE AS is registered as a limited company in Stad, Vestland with organisation number 919948825. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2017. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Frisørsalong og sal av varer og tenester som høyrer inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 470,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 470,000
Equity
NOK 576,000
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns CUT HÅR OG VELVÆRE AS?

YVONNE BERRAK STARHEIMSVIK
CUT HÅR OG VELVÆRE AS
NOK 3.9m rev. · NOK 470,000 profit

CUT HÅR OG VELVÆRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CUT HÅR OG VELVÆRE AS

Who owns CUT HÅR OG VELVÆRE AS?

YVONNE BERRAK STARHEIMSVIK is the largest registered owner, with 100.0%.

What is the revenue of CUT HÅR OG VELVÆRE AS?

CUT HÅR OG VELVÆRE AS had revenue of NOK 3.9m in 2025.

Who is the general manager of CUT HÅR OG VELVÆRE AS?

Yvonne Berrak Starheimsvik is registered as general manager of CUT HÅR OG VELVÆRE AS.

Where is CUT HÅR OG VELVÆRE AS based?

CUT HÅR OG VELVÆRE AS has its business address in Nordfjordeid.

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.