BIZTRAC BETA
Rental and operating of own or leased real estate

HADELANDSPARKEN 2 AS

Org. no. 929489764 Limited company (AS) Lunner Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −30,000
Equity NOK 414,000
Incorporated 2022
Share capital NOK 280,000

Signals

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

HADELANDSPARKEN 2 AS is registered as a limited company in Lunner, Akershus with organisation number 929489764. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 280,000, divided into 1000 shares. The company's stated purpose is: “Kjøpe, selge, utvikle, feste eller leie/leie ut eiendommer og/eller forestå oppføring og drift av eiendommer. Kjøp og salg av kapitalkrevende varer. Selskapet kan gjennom stiftelse av aksjeselskaper, kjøp av aksjer/andeler eller på annen måte også være interessent i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −30,000
Equity
NOK 414,000
Est. value
NOK 378,000

Financial health · 2024

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

Who owns HADELANDSPARKEN 2 AS?

LP-INVEST ROA AS
HADELANDSPARKEN 2 AS
· NOK −30,000 profit

HADELANDSPARKEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HADELANDSPARKEN 2 AS er morselskap for 11 datterselskaper:

Frequently asked questions about HADELANDSPARKEN 2 AS

Who owns HADELANDSPARKEN 2 AS?

LP-INVEST ROA AS is the largest registered owner, with 100.0%.

Who is the general manager of HADELANDSPARKEN 2 AS?

Tore Lynnebakken is registered as general manager of HADELANDSPARKEN 2 AS.

Where is HADELANDSPARKEN 2 AS based?

HADELANDSPARKEN 2 AS has its business address in Roa.

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.