BIZTRAC BETA
Hairdressing and barber activities

THINK HAIR WEAR SANDSLI AS

Org. no. 960368614 Limited company (AS) Bergen Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 581,000
Equity NOK 378,000
Incorporated 1991
Employees 5
Share capital NOK 150,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

THINK HAIR WEAR SANDSLI AS is registered as a limited company in Bergen, Vestland with organisation number 960368614. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1991 and has 5 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Handel samt frisørsalong, og hva herved naturlig står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 581,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 581,000
Equity
NOK 378,000
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns THINK HAIR WEAR SANDSLI AS?

THW HOLDINGS AS
THINK HAIR WEAR SANDSLI AS
NOK 5.0m rev. · NOK 581,000 profit

THINK HAIR WEAR SANDSLI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THINK HAIR WEAR SANDSLI AS

Who owns THINK HAIR WEAR SANDSLI AS?

THW HOLDINGS AS is the largest registered owner, with 100.0%.

What is the revenue of THINK HAIR WEAR SANDSLI AS?

THINK HAIR WEAR SANDSLI AS had revenue of NOK 5.0m in 2025.

Where is THINK HAIR WEAR SANDSLI AS based?

THINK HAIR WEAR SANDSLI AS has its business address in Sandsli.

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.