BIZTRAC BETA
Hairdressing and barber activities

LW STUDIO AS

Org. no. 995007169 Limited company (AS) Asker Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK −79,000
Equity NOK −101,000
Incorporated 2009
Share capital NOK 100,000

Signals

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

LW STUDIO AS is registered as a limited company in Asker, Akershus with organisation number 995007169. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eierselskap og driftsselskap for LW Studio AS innenfor frisør, blomster og velvære og tilhørende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −79,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −79,000
Equity
NOK −101,000

Financial health · 2025

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

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

Who owns LW STUDIO AS?

LENE ERIKSEN
LW STUDIO AS
NOK 1.5m rev. · NOK −79,000 profit

LW STUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LW STUDIO AS

Who owns LW STUDIO AS?

LENE ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of LW STUDIO AS?

LW STUDIO AS had revenue of NOK 1.5m in 2025.

Who is the general manager of LW STUDIO AS?

Lene Eriksen is registered as general manager of LW STUDIO AS.

Where is LW STUDIO AS based?

LW STUDIO AS has its business address in Vollen.

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.