BIZTRAC BETA
Hairdressing and barber activities

LUGN FRISØR AS

Org. no. 930485179 Limited company (AS) Lunner Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK −58,000
Equity NOK 2.0m
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−58k kr).

LUGN FRISØR AS is registered as a limited company in Lunner, Akershus with organisation number 930485179. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Frisørsalong med tilhørende tjenester og varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK −58,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK −58,000
Equity
NOK 2.0m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns LUGN FRISØR AS?

JANNE MIKKELSEN NORDGÅRD
LUGN FRISØR AS
NOK 1.8m rev. · NOK −58,000 profit

LUGN FRISØR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LUGN FRISØR AS own?

LUGN FRISØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LUGN FRISØR AS

Who owns LUGN FRISØR AS?

JANNE MIKKELSEN NORDGÅRD is the largest registered owner, with 90.0%.

What is the revenue of LUGN FRISØR AS?

LUGN FRISØR AS had revenue of NOK 1.8m in 2024.

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

Janne Mikkelsen Nordgård is registered as general manager of LUGN FRISØR AS.

Where is LUGN FRISØR AS based?

LUGN FRISØR AS has its business address in Roa.

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.