BIZTRAC BETA
Hairdressing and barber activities

KINGS CUT AS

Org. no. 934267788 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −54,000
Equity NOK −16,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

KINGS CUT AS is registered as a limited company in Oslo, Oslo with organisation number 934267788. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å tilby tjenester og produkter innenfor frisering og annen skjønnhetspleie, herunder frisørtjenester og salg av produkter, samt investeringer og deltakelse i andre selskaper med liknende formål og hva hermed naturlig står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −54,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −54,000
Equity
NOK −16,000

Financial health · 2025

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

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

Who owns KINGS CUT AS?

CHOPSHOPAGENCY AS
KINGS CUT AS
NOK 1.2m rev. · NOK −54,000 profit

KINGS CUT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KINGS CUT AS

Who owns KINGS CUT AS?

CHOPSHOPAGENCY AS is the largest registered owner, with 60.0%.

What is the revenue of KINGS CUT AS?

KINGS CUT AS had revenue of NOK 1.2m in 2025.

Where is KINGS CUT AS based?

KINGS CUT AS has its business address in Oslo.

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.