BIZTRAC BETA
Hairdressing and barber activities

UPPERCUT FRISØR AS

Org. no. 995498340 Limited company (AS) Oppdal Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 604,000
Equity NOK 123,000
Incorporated 2010
Employees 8
Share capital NOK 102,000

UPPERCUT FRISØR AS is registered as a limited company in Oppdal, Trøndelag with organisation number 995498340. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2010 and has 8 registered employees. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Drive frisørsalong, samt salg av tjenester og produkter som naturlig hører sammen med dette. Videre investeringer i selskaper som naturlig hører sammen med dette og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 604,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 604,000
Equity
NOK 123,000
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns UPPERCUT FRISØR AS?

KRISTIN HAGEN
UPPERCUT FRISØR AS
NOK 3.7m rev. · NOK 604,000 profit

UPPERCUT FRISØR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about UPPERCUT FRISØR AS

Who owns UPPERCUT FRISØR AS?

KRISTIN HAGEN is the largest registered owner, with 33.3%.

What is the revenue of UPPERCUT FRISØR AS?

UPPERCUT FRISØR AS had revenue of NOK 3.7m in 2025.

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

Siw Sundsethaug is registered as general manager of UPPERCUT FRISØR AS.

Where is UPPERCUT FRISØR AS based?

UPPERCUT FRISØR AS has its business address in Oppdal.

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.