BIZTRAC BETA
Hairdressing and barber activities

ELGESETER HÅRDESIGN AS

Org. no. 974528894 Limited company (AS) Trondheim Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 33,000
Equity NOK 375,000
Incorporated 1995
Employees 5
Share capital NOK 50,000

ELGESETER HÅRDESIGN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 974528894. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1995 and has 5 registered employees. Registered share capital is NOK 50,000, divided into 2000 shares. The company's stated purpose is: “Frisørvirksomhet samt ved aksjetegning eller på annen måte å bli delaktig i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 33,000
Equity
NOK 375,000
Est. value
NOK 314,000

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.2%
Good
Equity as a share of total capital

Who owns ELGESETER HÅRDESIGN AS?

HEGE MARGRETHE ARNTZEN
ELGESETER HÅRDESIGN AS
NOK 4.0m rev. · NOK 33,000 profit

ELGESETER HÅRDESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELGESETER HÅRDESIGN AS

Who owns ELGESETER HÅRDESIGN AS?

HEGE MARGRETHE ARNTZEN is the largest registered owner, with 100.0%.

What is the revenue of ELGESETER HÅRDESIGN AS?

ELGESETER HÅRDESIGN AS had revenue of NOK 4.0m in 2025.

Who is the general manager of ELGESETER HÅRDESIGN AS?

Hege Margrethe Arntzen is registered as general manager of ELGESETER HÅRDESIGN AS.

Where is ELGESETER HÅRDESIGN AS based?

ELGESETER HÅRDESIGN AS has its business address in Trondheim.

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.