BIZTRAC BETA
Hairdressing and barber activities

HØNEFOSS FRISØR AS

Org. no. 934971884 Limited company (AS) Ringerike Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −72,000
Equity NOK −43,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−43k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−72k kr).

HØNEFOSS FRISØR AS is registered as a limited company in Ringerike, Buskerud with organisation number 934971884. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Frisering og annen skjønnhetspleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −72,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −72,000
Equity
NOK −43,000

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-20.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HØNEFOSS FRISØR AS?

NAJI HAMED
HØNEFOSS FRISØR AS
NOK 1.4m rev. · NOK −72,000 profit

HØNEFOSS FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØNEFOSS FRISØR AS

Who owns HØNEFOSS FRISØR AS?

NAJI HAMED is the largest registered owner, with 100.0%.

What is the revenue of HØNEFOSS FRISØR AS?

HØNEFOSS FRISØR AS had revenue of NOK 1.4m in 2025.

Who is the general manager of HØNEFOSS FRISØR AS?

Naji Hamed is registered as general manager of HØNEFOSS FRISØR AS.

Where is HØNEFOSS FRISØR AS based?

HØNEFOSS FRISØR 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.