BIZTRAC BETA
Hairdressing and barber activities

LUGGEN AS

Org. no. 968360957 Limited company (AS) Sør-Varanger Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK −312,000
Equity NOK −179,000
Incorporated 1993
Employees 6
Share capital NOK 100,000

Signals

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

LUGGEN AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 968360957. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 1993 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Frisørvirksomhet, handel, konsulentvirksomhet og alt som har forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK −312,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK −312,000
Equity
NOK −179,000

Financial health · 2025

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

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

Who owns LUGGEN AS?

Bente Salmi
LUGGEN AS
NOK 5.5m rev. · NOK −312,000 profit

LUGGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUGGEN AS

Who owns LUGGEN AS?

Bente Salmi is the largest registered owner, with 100.0%.

What is the revenue of LUGGEN AS?

LUGGEN AS had revenue of NOK 5.5m in 2025.

Who is the general manager of LUGGEN AS?

Janne Martinsen is registered as general manager of LUGGEN AS.

Where is LUGGEN AS based?

LUGGEN AS has its business address in Kirkenes.

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.