BIZTRAC BETA
Hairdressing and barber activities

CLIP & STYLING FRISØR AS

Org. no. 977278597 Limited company (AS) Klepp Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −2,000
Equity NOK 309,000
Incorporated 1997
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

CLIP & STYLING FRISØR AS is registered as a limited company in Klepp, Rogaland with organisation number 977278597. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1997. Registered share capital is NOK 100,000. The company's stated purpose is: “Frisørsalong og alt som hermed står i forbindelse, herunder deltakelse i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −2,000
Equity
NOK 309,000
Est. value
NOK 713,000

Financial health · 2024

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

Who owns CLIP & STYLING FRISØR AS?

SOL AARRE
CLIP & STYLING FRISØR AS
NOK 1.5m rev. · NOK −2,000 profit

CLIP & STYLING FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CLIP & STYLING FRISØR AS

Who owns CLIP & STYLING FRISØR AS?

SOL AARRE is the largest registered owner, with 100.0%.

What is the revenue of CLIP & STYLING FRISØR AS?

CLIP & STYLING FRISØR AS had revenue of NOK 1.5m in 2024.

Who is the general manager of CLIP & STYLING FRISØR AS?

Sol Aarre is registered as general manager of CLIP & STYLING FRISØR AS.

Where is CLIP & STYLING FRISØR AS based?

CLIP & STYLING FRISØR AS has its business address in Kleppe.

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.