BIZTRAC BETA
Rental and operating of own or leased real estate

LUNDE EIENDOMSFORVALTNING AS

Org. no. 832010642 Limited company (AS) Moss Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 634,000
Operating profit NOK 469,000
Equity NOK 1.6m
Incorporated 2023
Share capital NOK 50,000

Signals

1 flags
  • Nylig endring 2026-05-14 Adresseendring registrert 2026-05-14.

LUNDE EIENDOMSFORVALTNING AS is registered as a limited company in Moss, Østfold with organisation number 832010642. 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 50,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom, aksjer, andre virksomheter samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 634,000 in revenue and NOK 469,000 in operating profit.

Key figures · 2025

Revenue
NOK 634,000
Operating profit
NOK 469,000
Equity
NOK 1.6m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns LUNDE EIENDOMSFORVALTNING AS?

LUNDES HOLDING AS
LUNDE EIENDOMSFORVALTNING AS
NOK 634,000 rev. · NOK 469,000 profit

LUNDE EIENDOMSFORVALTNING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUNDE EIENDOMSFORVALTNING AS

Who owns LUNDE EIENDOMSFORVALTNING AS?

LUNDES HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of LUNDE EIENDOMSFORVALTNING AS?

LUNDE EIENDOMSFORVALTNING AS had revenue of NOK 634,000 in 2025.

Where is LUNDE EIENDOMSFORVALTNING AS based?

LUNDE EIENDOMSFORVALTNING AS has its business address in Dilling.

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.