BIZTRAC BETA
Hairdressing and barber activities

SAXEN FRISØRSALONG AS

Org. no. 995312395 Limited company (AS) Stavanger Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 385,000
Equity NOK 1.2m
Incorporated 2010
Share capital NOK 388,000

SAXEN FRISØRSALONG AS is registered as a limited company in Stavanger, Rogaland with organisation number 995312395. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2010. Registered share capital is NOK 388,000, divided into 388 shares. The company's stated purpose is: “Drift av frisøsalong, kjøp og salg av skjønnhetsprodukter samt alt hva hermed står i forbindelse, herunder deltakelse i selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 385,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 385,000
Equity
NOK 1.2m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns SAXEN FRISØRSALONG AS?

HEIDI ESPEDAL ELTERVÅG
SAXEN FRISØRSALONG AS
NOK 2.3m rev. · NOK 385,000 profit

SAXEN FRISØRSALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAXEN FRISØRSALONG AS

Who owns SAXEN FRISØRSALONG AS?

HEIDI ESPEDAL ELTERVÅG is the largest registered owner, with 100.0%.

What is the revenue of SAXEN FRISØRSALONG AS?

SAXEN FRISØRSALONG AS had revenue of NOK 2.3m in 2025.

Who is the general manager of SAXEN FRISØRSALONG AS?

Heidi Espedal Eltervåg is registered as general manager of SAXEN FRISØRSALONG AS.

Where is SAXEN FRISØRSALONG AS based?

SAXEN FRISØRSALONG AS has its business address in Hafrsfjord.

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.