BIZTRAC BETA
Hairdressing and barber activities

FIX DAME OG HERREFRISØR AS

Org. no. 917419078 Limited company (AS) Jevnaker Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 219,000
Equity NOK 606,000
Incorporated 2016
Employees 7
Share capital NOK 30,000

FIX DAME OG HERREFRISØR AS is registered as a limited company in Jevnaker, Akershus with organisation number 917419078. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Dame og herrefrisør salong og det som dermed hører med.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 219,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 219,000
Equity
NOK 606,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns FIX DAME OG HERREFRISØR AS?

KRISTIN GRANDE
FIX DAME OG HERREFRISØR AS
NOK 2.8m rev. · NOK 219,000 profit

FIX DAME OG HERREFRISØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FIX DAME OG HERREFRISØR AS

Who owns FIX DAME OG HERREFRISØR AS?

KRISTIN GRANDE is the largest registered owner, with 50.0%.

What is the revenue of FIX DAME OG HERREFRISØR AS?

FIX DAME OG HERREFRISØR AS had revenue of NOK 2.8m in 2025.

Who is the general manager of FIX DAME OG HERREFRISØR AS?

Vivi Gulbrandsen Engeli is registered as general manager of FIX DAME OG HERREFRISØR AS.

Where is FIX DAME OG HERREFRISØR AS based?

FIX DAME OG HERREFRISØR AS has its business address in Jevnaker.

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.