BIZTRAC BETA
Hairdressing and barber activities

PAPILJOTTEN FRISØR AS

Org. no. 974484552 Limited company (AS) Kvam Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 642,000
Equity NOK 1.5m
Incorporated 1995
Employees 6
Share capital NOK 100,000

PAPILJOTTEN FRISØR AS is registered as a limited company in Kvam, Vestland with organisation number 974484552. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1995 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drift av frisørsalong og hva dermed står i forbindelse, herunder ved innskudd av kapital, eventuelt ved aksjetegning å delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 642,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 642,000
Equity
NOK 1.5m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns PAPILJOTTEN FRISØR AS?

MALENA ERIKSON SEIM
PAPILJOTTEN FRISØR AS
NOK 5.6m rev. · NOK 642,000 profit

PAPILJOTTEN FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAPILJOTTEN FRISØR AS

Who owns PAPILJOTTEN FRISØR AS?

MALENA ERIKSON SEIM is the largest registered owner, with 100.0%.

What is the revenue of PAPILJOTTEN FRISØR AS?

PAPILJOTTEN FRISØR AS had revenue of NOK 5.6m in 2025.

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

Malena Erikson Seim is registered as general manager of PAPILJOTTEN FRISØR AS.

Where is PAPILJOTTEN FRISØR AS based?

PAPILJOTTEN FRISØR AS has its business address in Norheimsund.

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.