BIZTRAC BETA
Rental and operating of own or leased real estate

ELVERUM RETAIL PARK AS

Org. no. 917424160 Limited company (AS) Kongsvinger Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −36,000
Equity NOK 63.2m
Incorporated 2016
Share capital NOK 51,000

Signals

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

ELVERUM RETAIL PARK AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 917424160. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 51,000, divided into 25730 shares. The company's stated purpose is: “Eie og drive selskaper som driver med eiendomserverv, eiendomsutvikling og drift, samt alt i forbindelse hermed, herunder å delta i andre selskaper med liknende virksomhet.”.

Key figures · 2024

Operating profit
NOK −36,000
Equity
NOK 63.2m
Est. value
NOK 57.6m

Financial health · 2024

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

Who owns ELVERUM RETAIL PARK AS?

ELVERUM UTVIKLING AS
ELVERUM RETAIL PARK AS
· NOK −36,000 profit

ELVERUM RETAIL PARK AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ELVERUM RETAIL PARK AS own?

ELVERUM RETAIL PARK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ELVERUM RETAIL PARK AS

Who owns ELVERUM RETAIL PARK AS?

ELVERUM UTVIKLING AS is the largest registered owner, with 60.4%.

Where is ELVERUM RETAIL PARK AS based?

ELVERUM RETAIL PARK AS has its business address in Kongsvinger.

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.