BIZTRAC BETA
Hairdressing and barber activities

POP INN FRISØRSALONG AS

Org. no. 984381255 Limited company (AS) Karmøy Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 139,000
Equity NOK 137,000
Incorporated 2002
Share capital NOK 100,000

POP INN FRISØRSALONG AS is registered as a limited company in Karmøy, Rogaland with organisation number 984381255. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Frisørsalong, salg og service, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 139,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 139,000
Equity
NOK 137,000
Est. value
NOK 597,000

Financial health · 2024

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

Who owns POP INN FRISØRSALONG AS?

ELISE MARIE AARØY VIKSE
POP INN FRISØRSALONG AS
NOK 2.2m rev. · NOK 139,000 profit

POP INN FRISØRSALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POP INN FRISØRSALONG AS

Who owns POP INN FRISØRSALONG AS?

ELISE MARIE AARØY VIKSE is the largest registered owner, with 100.0%.

What is the revenue of POP INN FRISØRSALONG AS?

POP INN FRISØRSALONG AS had revenue of NOK 2.2m in 2025.

Who is the general manager of POP INN FRISØRSALONG AS?

Elise Marie Aarøy Vikse is registered as general manager of POP INN FRISØRSALONG AS.

Where is POP INN FRISØRSALONG AS based?

POP INN FRISØRSALONG AS has its business address in Åkrehamn.

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.