BIZTRAC BETA
Hairdressing and barber activities

SALONG94 FRISØR AS

Org. no. 968595687 Limited company (AS) Rana Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK −20,000
Equity NOK 1.3m
Incorporated 1994
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−20k kr).

SALONG94 FRISØR AS is registered as a limited company in Rana, Nordland with organisation number 968595687. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1994 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Drive frisørsalong, samt hva hermed står i forbindelse. Selskapet kan også delta i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK −20,000
Equity
NOK 1.3m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns SALONG94 FRISØR AS?

SIV ELIASSEN BOGEN
SALONG94 FRISØR AS
NOK 3.7m rev. · NOK −20,000 profit

SALONG94 FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SALONG94 FRISØR AS

Who owns SALONG94 FRISØR AS?

SIV ELIASSEN BOGEN is the largest registered owner, with 100.0%.

What is the revenue of SALONG94 FRISØR AS?

SALONG94 FRISØR AS had revenue of NOK 3.7m in 2025.

Who is the general manager of SALONG94 FRISØR AS?

Siv Eliassen Bogen is registered as general manager of SALONG94 FRISØR AS.

Where is SALONG94 FRISØR AS based?

SALONG94 FRISØR AS has its business address in Mo I Rana.

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.