BIZTRAC BETA
Hairdressing and barber activities

KING CUTS AS

Org. no. 930785814 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 226,000
Operating profit NOK −24,000
Equity NOK −42,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−42k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).

KING CUTS AS is registered as a limited company in Kristiansand, Agder with organisation number 930785814. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Frisørsalong, hårpleie, hudpleie, styling, barbering. Vaske, klippe og føne hår. Salg av hår og hudprodukter relaterte til yrket. Salg og servise. Utleie av frisør stol.”. The most recent filed accounts, for the 2025 financial year, show NOK 226,000 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 226,000
Operating profit
NOK −24,000
Equity
NOK −42,000

Financial health · 2025

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-92.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KING CUTS AS?

KHALED ADAM MUSTAFA MAHMOUD
KING CUTS AS
NOK 226,000 rev. · NOK −24,000 profit

KING CUTS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KING CUTS AS

Who owns KING CUTS AS?

KHALED ADAM MUSTAFA MAHMOUD is the largest registered owner, with 100.0%.

What is the revenue of KING CUTS AS?

KING CUTS AS had revenue of NOK 226,000 in 2025.

Where is KING CUTS AS based?

KING CUTS AS has its business address in Kristiansand S.

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.