BIZTRAC BETA
Rental and operating of own or leased real estate

LESU AS

Org. no. 981683749 Limited company (AS) Ålesund Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 482,000
Operating profit NOK −216,000
Equity NOK 15.4m
Incorporated 2000
Share capital NOK 3.4m

Signals

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

LESU AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 981683749. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 3.4m, divided into 6850 shares. The company's stated purpose is: “Selskapets formål er å drive med produksjon, ergrosvirksomhet og handel samt investering i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 482,000 in revenue and NOK −216,000 in operating profit.

Key figures · 2025

Revenue
NOK 482,000
Operating profit
NOK −216,000
Equity
NOK 15.4m
Est. value
NOK 10.7m

Financial health · 2025

Liquidity
27.50
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
83.3%
Very good
Equity as a share of total capital

Who owns LESU AS?

TOVE MARIT SUNDE
LESU AS
NOK 482,000 rev. · NOK −216,000 profit

LESU AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LESU AS own?

LESU AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about LESU AS

Who owns LESU AS?

TOVE MARIT SUNDE is the largest registered owner, with 100.0%.

What is the revenue of LESU AS?

LESU AS had revenue of NOK 482,000 in 2025.

Who is the general manager of LESU AS?

Tove Marit Sunde is registered as general manager of LESU AS.

Where is LESU AS based?

LESU AS has its business address in Ålesund.

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.