BIZTRAC BETA
Rental and operating of own or leased real estate

LEPSØY EIENDOMSSELSKAP AS

Org. no. 958589808 Limited company (AS) Haram Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 120,000
Operating profit NOK 27,000
Equity NOK 672,000
Incorporated 1990
Share capital NOK 100,000

LEPSØY EIENDOMSSELSKAP AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 958589808. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Eige og leige ut fast eigedom, samt anna verksemd i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 120,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2025

Revenue
NOK 120,000
Operating profit
NOK 27,000
Equity
NOK 672,000
Est. value
NOK 539,000

Financial health · 2025

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

Who owns LEPSØY EIENDOMSSELSKAP AS?

LISBETH FARSTAD
LEPSØY EIENDOMSSELSKAP AS
NOK 120,000 rev. · NOK 27,000 profit

LEPSØY EIENDOMSSELSKAP AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEPSØY EIENDOMSSELSKAP AS

Who owns LEPSØY EIENDOMSSELSKAP AS?

LISBETH FARSTAD is the largest registered owner, with 20.0%.

What is the revenue of LEPSØY EIENDOMSSELSKAP AS?

LEPSØY EIENDOMSSELSKAP AS had revenue of NOK 120,000 in 2025.

Who is the general manager of LEPSØY EIENDOMSSELSKAP AS?

Odd Asle Farstad is registered as general manager of LEPSØY EIENDOMSSELSKAP AS.

Where is LEPSØY EIENDOMSSELSKAP AS based?

LEPSØY EIENDOMSSELSKAP AS has its business address in Kjerstad.

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.