BIZTRAC BETA
Hairdressing and barber activities

KOMPONISTEN FRISØRSALONG AS

Org. no. 973192302 Limited company (AS) Kristiansand Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 209,000
Equity NOK 347,000
Incorporated 1995
Employees 5
Share capital NOK 100,000

KOMPONISTEN FRISØRSALONG AS is registered as a limited company in Kristiansand, Agder with organisation number 973192302. 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 100,000. The company's stated purpose is: “Frisørvirksomhet og all virksomhet som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 209,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 209,000
Equity
NOK 347,000
Est. value
NOK 997,000

Financial health · 2025

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

Who owns KOMPONISTEN FRISØRSALONG AS?

INGER HOLSKOG
KOMPONISTEN FRISØRSALONG AS
NOK 2.3m rev. · NOK 209,000 profit

KOMPONISTEN FRISØRSALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOMPONISTEN FRISØRSALONG AS

Who owns KOMPONISTEN FRISØRSALONG AS?

INGER HOLSKOG is the largest registered owner, with 100.0%.

What is the revenue of KOMPONISTEN FRISØRSALONG AS?

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

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

Inger Holskog is registered as general manager of KOMPONISTEN FRISØRSALONG AS.

Where is KOMPONISTEN FRISØRSALONG AS based?

KOMPONISTEN FRISØRSALONG AS has its business address in Kristiansand S.

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.