BIZTRAC BETA
Hairdressing and barber activities

PÅ HENGENDE HÅRET AS

Org. no. 935328292 Limited company (AS) Ringerike Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 650,000
Equity NOK 464,000
Incorporated 2025
Employees 6
Share capital NOK 30,000

PÅ HENGENDE HÅRET AS is registered as a limited company in Ringerike, Buskerud with organisation number 935328292. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2025 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Frisørvirksomhet og annen skjønnhetspleie og det som dertil hører, kjøp og salg av tilhørende produkter, investeringer i aksjer og andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 650,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 650,000
Equity
NOK 464,000
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns PÅ HENGENDE HÅRET AS?

KAMILLA LØKKEN
PÅ HENGENDE HÅRET AS
NOK 3.0m rev. · NOK 650,000 profit

PÅ HENGENDE HÅRET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PÅ HENGENDE HÅRET AS

Who owns PÅ HENGENDE HÅRET AS?

KAMILLA LØKKEN is the largest registered owner, with 100.0%.

What is the revenue of PÅ HENGENDE HÅRET AS?

PÅ HENGENDE HÅRET AS had revenue of NOK 3.0m in 2025.

Who is the general manager of PÅ HENGENDE HÅRET AS?

Kamilla Løkken is registered as general manager of PÅ HENGENDE HÅRET AS.

Where is PÅ HENGENDE HÅRET AS based?

PÅ HENGENDE HÅRET AS has its business address in Hønefoss.

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.