BIZTRAC BETA
Rental and operating of own or leased real estate

LEHA EIENDOM AS

Org. no. 931375431 Limited company (AS) Vestvågøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 448,000
Operating profit NOK 259,000
Equity NOK 157,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LEHA EIENDOM AS is registered as a limited company in Vestvågøy, Nordland with organisation number 931375431. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering, drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 448,000 in revenue and NOK 259,000 in operating profit.

Key figures · 2025

Revenue
NOK 448,000
Operating profit
NOK 259,000
Equity
NOK 157,000
Est. value
NOK 604,000

Financial health · 2025

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

Who owns LEHA EIENDOM AS?

HAA HAVET HOLDING AS
LEHA EIENDOM AS
NOK 448,000 rev. · NOK 259,000 profit

LEHA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEHA EIENDOM AS

Who owns LEHA EIENDOM AS?

HAA HAVET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LEHA EIENDOM AS?

LEHA EIENDOM AS had revenue of NOK 448,000 in 2025.

Who is the general manager of LEHA EIENDOM AS?

Hans Arne Arntzen is registered as general manager of LEHA EIENDOM AS.

Where is LEHA EIENDOM AS based?

LEHA EIENDOM 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.