BIZTRAC BETA
Rental and operating of own or leased real estate

LUND EIENDOM AS

Org. no. 914006295 Limited company (AS) Nord-Fron Incorporated 1969 Active
Ownership graph ↗
Revenue 2025 NOK 341,000
Operating profit NOK −125,000
Equity NOK 11.2m
Incorporated 1969
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−125k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LUND EIENDOM AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 914006295. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1969. Registered share capital is NOK 100,000. The company's stated purpose is: “Investeringer i næringsvirksomhet, herunder aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 341,000 in revenue and NOK −125,000 in operating profit.

Key figures · 2025

Revenue
NOK 341,000
Operating profit
NOK −125,000
Equity
NOK 11.2m
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns LUND EIENDOM AS?

LUNCON HOLDING AS
LUND EIENDOM AS
NOK 341,000 rev. · NOK −125,000 profit

LUND EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Group structure

LUND EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about LUND EIENDOM AS

Who owns LUND EIENDOM AS?

LUNCON HOLDING AS is the largest registered owner, with 66.7%.

What is the revenue of LUND EIENDOM AS?

LUND EIENDOM AS had revenue of NOK 341,000 in 2025.

Where is LUND EIENDOM AS based?

LUND EIENDOM AS has its business address in Vinstra.

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.