BIZTRAC BETA
Hairdressing and barber activities

SALONG IN AS

Org. no. 929313259 Limited company (AS) Surnadal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 54,000
Equity NOK 44,000
Incorporated 2022
Share capital NOK 30,000

SALONG IN AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 929313259. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisørvirksomhet, salg av frisørprodukter og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 54,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 54,000
Equity
NOK 44,000
Est. value
NOK 228,000

Financial health · 2025

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

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

Who owns SALONG IN AS?

BEATE HOLTEN
SALONG IN AS
NOK 1.8m rev. · NOK 54,000 profit

SALONG IN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SALONG IN AS

Who owns SALONG IN AS?

BEATE HOLTEN is the largest registered owner, with 50.0%.

What is the revenue of SALONG IN AS?

SALONG IN AS had revenue of NOK 1.8m in 2025.

Who is the general manager of SALONG IN AS?

Beate Holten is registered as general manager of SALONG IN AS.

Where is SALONG IN AS based?

SALONG IN AS has its business address in Surnadal.

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.