BIZTRAC BETA
Rental and operating of own or leased real estate

LEPSØY INVEST AS

Org. no. 932206773 Limited company (AS) Haram Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 42,000
Operating profit NOK −47,000
Equity NOK 441,000
Incorporated 2023
Share capital NOK 593,000

Signals

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

LEPSØY INVEST AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 932206773. 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 593,000, divided into 39500 shares. The company's stated purpose is: “Selskapet skal kjøp, selge, eie, leie og utleie av eiendom. Samt investere i selskaper i samme bransje.”. The most recent filed accounts, for the 2025 financial year, show NOK 42,000 in revenue and NOK −47,000 in operating profit.

Key figures · 2025

Revenue
NOK 42,000
Operating profit
NOK −47,000
Equity
NOK 441,000
Est. value
NOK 365,000

Financial health · 2025

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

Who owns LEPSØY INVEST AS?

JAN PETTER LAUSUND
LEPSØY INVEST AS
NOK 42,000 rev. · NOK −47,000 profit

LEPSØY INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEPSØY INVEST AS

Who owns LEPSØY INVEST AS?

JAN PETTER LAUSUND is the largest registered owner, with 50.0%.

What is the revenue of LEPSØY INVEST AS?

LEPSØY INVEST AS had revenue of NOK 42,000 in 2025.

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

Jan Petter Lausund is registered as general manager of LEPSØY INVEST AS.

Where is LEPSØY INVEST AS based?

LEPSØY INVEST 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.