BIZTRAC BETA
Rental and operating of own or leased real estate

LAMOPARKEN EIENDOM AS

Org. no. 921976852 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 551,000
Operating profit NOK −82,000
Equity NOK 2.3m
Incorporated 2018
Share capital NOK 97,000

Signals

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

LAMOPARKEN EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921976852. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 97,000, divided into 969656 shares. The company's stated purpose is: “Drift og utleie av eiendom samt relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 551,000 in revenue and NOK −82,000 in operating profit.

Key figures · 2024

Revenue
NOK 551,000
Operating profit
NOK −82,000
Equity
NOK 2.3m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns LAMOPARKEN EIENDOM AS?

NIDAROS VS AS
LAMOPARKEN EIENDOM AS
NOK 551,000 rev. · NOK −82,000 profit

LAMOPARKEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAMOPARKEN EIENDOM AS

Who owns LAMOPARKEN EIENDOM AS?

NIDAROS VS AS is the largest registered owner, with 100.0%.

What is the revenue of LAMOPARKEN EIENDOM AS?

LAMOPARKEN EIENDOM AS had revenue of NOK 551,000 in 2024.

Where is LAMOPARKEN EIENDOM AS based?

LAMOPARKEN EIENDOM AS has its business address in Trondheim.

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.