BIZTRAC BETA
Hairdressing and barber activities

SALONG CAPELLI SANI AS

Org. no. 988492175 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 153,000
Equity NOK 242,000
Incorporated 2005
Share capital NOK 100,000

SALONG CAPELLI SANI AS is registered as a limited company in Oslo, Oslo with organisation number 988492175. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Frisørsalong med hår, negle- og kroppsbehandling og salg av tilhørende produkter, herunder deltagelse i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 153,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 153,000
Equity
NOK 242,000
Est. value
NOK 722,000

Financial health · 2025

Liquidity
2.63
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.1%
Very good
Equity as a share of total capital

Who owns SALONG CAPELLI SANI AS?

BARDONJA ISMAILOVSKA
SALONG CAPELLI SANI AS
NOK 1.1m rev. · NOK 153,000 profit

SALONG CAPELLI SANI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALONG CAPELLI SANI AS

Who owns SALONG CAPELLI SANI AS?

BARDONJA ISMAILOVSKA is the largest registered owner, with 100.0%.

What is the revenue of SALONG CAPELLI SANI AS?

SALONG CAPELLI SANI AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SALONG CAPELLI SANI AS?

Bardonja Ismailovska is registered as general manager of SALONG CAPELLI SANI AS.

Where is SALONG CAPELLI SANI AS based?

SALONG CAPELLI SANI 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.