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

LECA HOLDING AS

Org. no. 921621728 Limited company (AS) Vestvågøy Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 624,000
Incorporated 2018
Share capital NOK 50,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LECA HOLDING AS is registered as a limited company in Vestvågøy, Nordland with organisation number 921621728. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2018. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Investering og eierskap i øvrige selskaper, samt øvrige finansielle investeringer.”.

Key figures · 2025

Operating profit
NOK −5,000
▼ −19 %
Equity
NOK 624,000
▼ −33 %
Est. value
NOK 826,000

Financial health · 2025

Liquidity
2.58
Very good
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
75.3%
Very good
Equity as a share of total capital

Who owns LECA HOLDING AS?

LECA HOLDING AS
· NOK −5,000 profit

LECA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LECA HOLDING AS own?

LECA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LECA HOLDING AS

Who owns LECA HOLDING AS?

Lena Carin Andersen is the largest registered owner, with 100.0%.

Who is the general manager of LECA HOLDING AS?

Lena Carin Andersen is registered as general manager of LECA HOLDING AS.

Where is LECA HOLDING AS based?

LECA HOLDING AS has its business address in Leknes.

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.