BIZTRAC BETA
Hairdressing and barber activities

CLEAN CUT FRISØR OG BARBERSTUE AS

Org. no. 925306320 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 106,000
Equity NOK 149,000
Incorporated 2020
Share capital NOK 30,000

CLEAN CUT FRISØR OG BARBERSTUE AS is registered as a limited company in Bærum, Akershus with organisation number 925306320. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisør og Barberstue.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 106,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 106,000
Equity
NOK 149,000
Est. value
NOK 481,000

Financial health · 2024

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

Who owns CLEAN CUT FRISØR OG BARBERSTUE AS?

BJØRN GUTTORMSEN
CLEAN CUT FRISØR OG BARBERSTUE AS
NOK 1.0m rev. · NOK 106,000 profit

CLEAN CUT FRISØR OG BARBERSTUE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CLEAN CUT FRISØR OG BARBERSTUE AS

Who owns CLEAN CUT FRISØR OG BARBERSTUE AS?

BJØRN GUTTORMSEN is the largest registered owner, with 100.0%.

What is the revenue of CLEAN CUT FRISØR OG BARBERSTUE AS?

CLEAN CUT FRISØR OG BARBERSTUE AS had revenue of NOK 1.0m in 2025.

Who is the general manager of CLEAN CUT FRISØR OG BARBERSTUE AS?

Bjørn Guttormsen is registered as general manager of CLEAN CUT FRISØR OG BARBERSTUE AS.

Where is CLEAN CUT FRISØR OG BARBERSTUE AS based?

CLEAN CUT FRISØR OG BARBERSTUE AS has its business address in Haslum.

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.