BIZTRAC BETA
Rental and operating of own or leased real estate

LERSTADVEIEN 539 AS

Org. no. 979893027 Limited company (AS) Ulstein Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 1.5m
Equity NOK 9.9m
Incorporated 1998
Share capital NOK 1.2m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LERSTADVEIEN 539 AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 979893027. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 1.2m, divided into 12000 shares. The company's stated purpose is: “Eie og drive eiendom, og dertil hørende virksomhet. Selskapet kan også delta i andre selskaper og virksomheter når dette samsvarer med selskapets formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 1.5m
Equity
NOK 9.9m
Est. value
NOK 10.1m

Financial health · 2024

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

Who owns LERSTADVEIEN 539 AS?

ÅLESUND UTVIKLING AS
LERSTADVEIEN 539 AS
NOK 3.8m rev. · NOK 1.5m profit

LERSTADVEIEN 539 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LERSTADVEIEN 539 AS

Who owns LERSTADVEIEN 539 AS?

ÅLESUND UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of LERSTADVEIEN 539 AS?

LERSTADVEIEN 539 AS had revenue of NOK 3.8m in 2024.

Where is LERSTADVEIEN 539 AS based?

LERSTADVEIEN 539 AS has its business address in Ulsteinvik.

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.