BIZTRAC BETA
Rental and operating of own or leased real estate

LUNDSTAD EIENDOM AS

Org. no. 996220052 Limited company (AS) Østre Toten Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 850,000
Operating profit NOK −54,000
Equity NOK 721,000
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).

LUNDSTAD EIENDOM AS is registered as a limited company in Østre Toten, Innlandet with organisation number 996220052. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom samt herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 850,000 in revenue and NOK −54,000 in operating profit.

Key figures · 2024

Revenue
NOK 850,000
Operating profit
NOK −54,000
Equity
NOK 721,000
Est. value
NOK 1.6m

Financial health · 2024

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns LUNDSTAD EIENDOM AS?

EINAR MARTMAN DYSTE
LUNDSTAD EIENDOM AS
NOK 850,000 rev. · NOK −54,000 profit

LUNDSTAD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUNDSTAD EIENDOM AS

Who owns LUNDSTAD EIENDOM AS?

EINAR MARTMAN DYSTE is the largest registered owner, with 50.0%.

What is the revenue of LUNDSTAD EIENDOM AS?

LUNDSTAD EIENDOM AS had revenue of NOK 850,000 in 2024.

Who is the general manager of LUNDSTAD EIENDOM AS?

Einar Martman Dyste is registered as general manager of LUNDSTAD EIENDOM AS.

Where is LUNDSTAD EIENDOM AS based?

LUNDSTAD EIENDOM AS has its business address in Kolbu.

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.