BIZTRAC BETA
Hairdressing and barber activities

SALHUS HÅRSTUDIO AS

Org. no. 932771918 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −498
Equity NOK 24,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−498 kr).

SALHUS HÅRSTUDIO AS is registered as a limited company in Bergen, Vestland with organisation number 932771918. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utføre frisørbehandlinger og salg av frisørprodukter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −498 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −498
Equity
NOK 24,000
Est. value
NOK 767,000

Financial health · 2024

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

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

Who owns SALHUS HÅRSTUDIO AS?

NATHALIE BERGAAS SALHUS
SALHUS HÅRSTUDIO AS
NOK 1.1m rev. · NOK −498 profit

SALHUS HÅRSTUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALHUS HÅRSTUDIO AS

Who owns SALHUS HÅRSTUDIO AS?

NATHALIE BERGAAS SALHUS is the largest registered owner, with 100.0%.

What is the revenue of SALHUS HÅRSTUDIO AS?

SALHUS HÅRSTUDIO AS had revenue of NOK 1.1m in 2024.

Who is the general manager of SALHUS HÅRSTUDIO AS?

Nathalie Bergaas Salhus is registered as general manager of SALHUS HÅRSTUDIO AS.

Where is SALHUS HÅRSTUDIO AS based?

SALHUS HÅRSTUDIO AS has its business address in Nyborg.

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.