BIZTRAC BETA
Hairdressing and barber activities

STUSSN HÅRSTUDIO AS

Org. no. 816958482 Limited company (AS) Alver Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 639,000
Equity NOK 641,000
Incorporated 2016
Share capital NOK 150,000

STUSSN HÅRSTUDIO AS is registered as a limited company in Alver, Vestland with organisation number 816958482. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2016. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Drift av frisørsalong, investering i fast eiendom, eiendomsdrift, handel, finansielle investeringer, konsulentvirksomhet og forretningsførsel. Selskapet kan engasjere seg i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 639,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 639,000
Equity
NOK 641,000
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns STUSSN HÅRSTUDIO AS?

STÅLE SLEIRE JOHANSEN
STUSSN HÅRSTUDIO AS
NOK 1.4m rev. · NOK 639,000 profit

STUSSN HÅRSTUDIO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STUSSN HÅRSTUDIO AS

Who owns STUSSN HÅRSTUDIO AS?

STÅLE SLEIRE JOHANSEN is the largest registered owner, with 83.0%.

What is the revenue of STUSSN HÅRSTUDIO AS?

STUSSN HÅRSTUDIO AS had revenue of NOK 1.4m in 2025.

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

Ståle Sleire Johansen is registered as general manager of STUSSN HÅRSTUDIO AS.

Where is STUSSN HÅRSTUDIO AS based?

STUSSN HÅRSTUDIO AS has its business address in Eikangervåg.

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.