BIZTRAC BETA
Hairdressing and barber activities

ISTANBUL FRISØRSALONG AS

Org. no. 923651349 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −70,000
Equity NOK −388,000
Incorporated 2019
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−388k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−70k kr).

ISTANBUL FRISØRSALONG AS is registered as a limited company in Oslo, Oslo with organisation number 923651349. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2019 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Dame og herre frisørsalong.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −70,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −70,000
Equity
NOK −388,000

Financial health · 2024

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

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

Who owns ISTANBUL FRISØRSALONG AS?

GYURHAN GYONGYOR GALIP
ISTANBUL FRISØRSALONG AS
NOK 1.5m rev. · NOK −70,000 profit

ISTANBUL FRISØRSALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ISTANBUL FRISØRSALONG AS

Who owns ISTANBUL FRISØRSALONG AS?

GYURHAN GYONGYOR GALIP is the largest registered owner, with 100.0%.

What is the revenue of ISTANBUL FRISØRSALONG AS?

ISTANBUL FRISØRSALONG AS had revenue of NOK 1.5m in 2024.

Where is ISTANBUL FRISØRSALONG AS based?

ISTANBUL FRISØRSALONG 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.