biztrac. BETA
COMPANY REGISTER PROFILE
834454122 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Beauty care and other beauty treatment activities

KING BARBERSHOP AS

Org. no. 834454122 Limited company (AS) Alstahaug Incorporated 2024 Active
Revenue 2025 NOK 1.6m
Operating profit NOK 75,000
Equity NOK 18,000
Incorporated 2024
Share capital NOK 30,000

KING BARBERSHOP AS is registered as a limited company in Alstahaug, Nordland with organisation number 834454122. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisørsalong.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 75,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +1732 %
Operating profit
NOK 75,000
▲ +193 %
Equity
NOK 18,000
▲ +132 %
Est. value
NOK 357,000

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
36.3%
Very good
Return on total assets
Solidity
7.3%
Weak
Equity as a share of total capital

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

Who owns KING BARBERSHOP AS?

KING BARBERSHOP AS
NOK 1.6m rev. · NOK 75,000 profit

KING BARBERSHOP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KING BARBERSHOP AS

Who owns KING BARBERSHOP AS?

Mohammad Abdulhamid Alsmadi is the largest registered owner, with 100.0%.

What is the revenue of KING BARBERSHOP AS?

KING BARBERSHOP AS had revenue of NOK 1.6m in 2025.

Who is the general manager of KING BARBERSHOP AS?

Mohammad Abdulhamid Alsmadi is registered as general manager of KING BARBERSHOP AS.

Where is KING BARBERSHOP AS based?

KING BARBERSHOP AS has its business address in Sandnessjøen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.