BIZTRAC BETA
Hairdressing and barber activities

COCO FRISØR AS

Org. no. 912022668 Limited company (AS) Stad Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 563,000
Equity NOK 238,000
Incorporated 2013
Employees 6
Share capital NOK 30,000

COCO FRISØR AS is registered as a limited company in Stad, Vestland with organisation number 912022668. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2013 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive frisørsalong og salg av hårpleieprodukter, samt deltagelse i andre selskaper med lignende formål, og virksomhet som naturlig er forbundet med dette, import/eksport, salg av handelsvarer, rådgivning og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 563,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 563,000
Equity
NOK 238,000
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns COCO FRISØR AS?

BERIT ENGEBRETSEN
COCO FRISØR AS
NOK 2.9m rev. · NOK 563,000 profit

COCO FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COCO FRISØR AS

Who owns COCO FRISØR AS?

BERIT ENGEBRETSEN is the largest registered owner, with 100.0%.

What is the revenue of COCO FRISØR AS?

COCO FRISØR AS had revenue of NOK 2.9m in 2024.

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

Berit Engebretsen is registered as general manager of COCO FRISØR AS.

Where is COCO FRISØR AS based?

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