biztrac. BETA
COMPANY REGISTER PROFILE
916754221 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

LILL HÅRDESIGN AS

Org. no. 916754221 Limited company (AS) Bergen Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 654,000
Operating profit NOK 48,000
Equity NOK 87,000
Incorporated 2016
Share capital NOK 30,000

LILL HÅRDESIGN AS is registered as a limited company in Bergen, Vestland with organisation number 916754221. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Frisørsalong og salg av produkter som er forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 654,000 in revenue and NOK 48,000 in operating profit.

Key figures · 2025

Revenue
NOK 654,000
▼ −10 %
Operating profit
NOK 48,000
▲ +305 %
Equity
NOK 87,000
▲ +108 %
Est. value
NOK 184,000

Financial health · 2025

Liquidity
2.15
Very good
Current assets ÷ current liabilities
Profitability
32.7%
Very good
Return on total assets
Solidity
53.5%
Weak
Equity as a share of total capital

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

Who owns LILL HÅRDESIGN AS?

LILL HÅRDESIGN AS
NOK 654,000 rev. · NOK 48,000 profit

LILL HÅRDESIGN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LILL HÅRDESIGN AS

Who owns LILL HÅRDESIGN AS?

Lill Karin Alræk is the largest registered owner, with 50.0%.

What is the revenue of LILL HÅRDESIGN AS?

LILL HÅRDESIGN AS had revenue of NOK 654,000 in 2025.

Who is the general manager of LILL HÅRDESIGN AS?

Lill Karin Alræk is registered as general manager of LILL HÅRDESIGN AS.

Where is LILL HÅRDESIGN AS based?

LILL HÅRDESIGN AS has its business address in Godvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.