BIZTRAC BETA
Beauty care and other beauty treatment activities

LEASPERLE HOLDING AS

Org. no. 931227025 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 47,000
Operating profit NOK −52,000
Equity NOK −2,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LEASPERLE HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 931227025. The business is classified under beauty care and other beauty treatment activities (NACE 96.220). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tjenester og kjøp og salg av produkter innen skjønnhetspleie og velvære.”. The most recent filed accounts, for the 2025 financial year, show NOK 47,000 in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 47,000
Operating profit
NOK −52,000
Equity
NOK −2,000

Financial health · 2025

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

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

Who owns LEASPERLE HOLDING AS?

Lea Løvik Sperle
LEASPERLE HOLDING AS
NOK 47,000 rev. · NOK −52,000 profit

LEASPERLE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEASPERLE HOLDING AS

Who owns LEASPERLE HOLDING AS?

Lea Løvik Sperle is the largest registered owner, with 100.0%.

What is the revenue of LEASPERLE HOLDING AS?

LEASPERLE HOLDING AS had revenue of NOK 47,000 in 2025.

Where is LEASPERLE HOLDING AS based?

LEASPERLE HOLDING AS has its business address in Ranheim.

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.