BIZTRAC BETA
Rental and operating of own or leased real estate

LENSVIK EIENDOM AS

Org. no. 924345349 Limited company (AS) Ålesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.5m
Equity NOK 9.8m
Incorporated 2019
Share capital NOK 4.0m

Signals

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

LENSVIK EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 924345349. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 4.0m, divided into 1500 shares. The company's stated purpose is: “Kjøp, utvikling, drift, forvaltning og salg av fast eiendom, samt det som naturlig står i forhold til dette, herunder også deltakelse i andre selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.5m
Equity
NOK 9.8m
Est. value
NOK 10.2m

Financial health · 2025

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

Who owns LENSVIK EIENDOM AS?

COM EIENDOM AS
LENSVIK EIENDOM AS
NOK 1.9m rev. · NOK 1.5m profit

LENSVIK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LENSVIK EIENDOM AS

Who owns LENSVIK EIENDOM AS?

COM EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of LENSVIK EIENDOM AS?

LENSVIK EIENDOM AS had revenue of NOK 1.9m in 2025.

Where is LENSVIK EIENDOM AS based?

LENSVIK EIENDOM 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.