BIZTRAC BETA
Hairdressing and barber activities

JK BARBER HOLDING AS

Org. no. 830179992 Limited company (AS) Nordre Follo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −528,000
Equity NOK −2.4m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−528k kr).

JK BARBER HOLDING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 830179992. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Formuesforvaltning, herunder investering i aksjer og andre verdipapirer samt annen tilknyttet virksomhet.”.

Key figures · 2024

Operating profit
NOK −528,000
Equity
NOK −2.4m

Financial health · 2024

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

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

Who owns JK BARBER HOLDING AS?

ALAN SIAMEND HANSEN
JK BARBER HOLDING AS
· NOK −528,000 profit

JK BARBER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JK BARBER HOLDING AS own?

JK BARBER HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about JK BARBER HOLDING AS

Who owns JK BARBER HOLDING AS?

ALAN SIAMEND HANSEN is the largest registered owner, with 100.0%.

Who is the general manager of JK BARBER HOLDING AS?

Alan Siamend Hansen is registered as general manager of JK BARBER HOLDING AS.

Where is JK BARBER HOLDING AS based?

JK BARBER HOLDING AS has its business address in Ski.

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.