BIZTRAC BETA
Hairdressing and barber activities

LITO HÅRDESIGN AS

Org. no. 898590372 Limited company (AS) Grimstad Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK −318,000
Equity NOK 97,000
Incorporated 2012
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−318k kr).

LITO HÅRDESIGN AS is registered as a limited company in Grimstad, Agder with organisation number 898590372. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2012 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Frisørsalong.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK −318,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK −318,000
Equity
NOK 97,000
Est. value
NOK 2.4m

Financial health · 2025

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

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

Who owns LITO HÅRDESIGN AS?

KATRINE JACOBSEN DOVLAND
LITO HÅRDESIGN AS
NOK 3.4m rev. · NOK −318,000 profit

LITO HÅRDESIGN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LITO HÅRDESIGN AS

Who owns LITO HÅRDESIGN AS?

KATRINE JACOBSEN DOVLAND is the largest registered owner, with 100.0%.

What is the revenue of LITO HÅRDESIGN AS?

LITO HÅRDESIGN AS had revenue of NOK 3.4m in 2025.

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

Mona Aasen Snøløs is registered as general manager of LITO HÅRDESIGN AS.

Where is LITO HÅRDESIGN AS based?

LITO HÅRDESIGN AS has its business address in Grimstad.

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.