BIZTRAC BETA
Hairdressing and barber activities

LUX DESIGN AS

Org. no. 914418453 Limited company (AS) Stord Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 955,000
Operating profit NOK 120,000
Equity NOK 31,000
Incorporated 2014
Share capital NOK 30,000

LUX DESIGN AS is registered as a limited company in Stord, Vestland with organisation number 914418453. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av frisørsalong samt annen virksomhet som naturlig faller inn under dette, herunder delta i andre selskap med liknende virksomhet. Samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 955,000 in revenue and NOK 120,000 in operating profit.

Key figures · 2025

Revenue
NOK 955,000
Operating profit
NOK 120,000
Equity
NOK 31,000
Est. value
NOK 431,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.3%
Weak
Equity as a share of total capital

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

Who owns LUX DESIGN AS?

LINDA OTTESEN
LUX DESIGN AS
NOK 955,000 rev. · NOK 120,000 profit

LUX DESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUX DESIGN AS

Who owns LUX DESIGN AS?

LINDA OTTESEN is the largest registered owner, with 100.0%.

What is the revenue of LUX DESIGN AS?

LUX DESIGN AS had revenue of NOK 955,000 in 2025.

Who is the general manager of LUX DESIGN AS?

Linda Ottesen is registered as general manager of LUX DESIGN AS.

Where is LUX DESIGN AS based?

LUX DESIGN AS has its business address in Sagvåg.

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.