BIZTRAC BETA
Rental and operating of own or leased real estate

GLOSTRUP RETAIL PARK AS

Org. no. 928122506 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −403,000
Equity NOK 205.7m
Incorporated 2021
Share capital NOK 1.0m

Signals

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

GLOSTRUP RETAIL PARK AS is registered as a limited company in Oslo, Oslo with organisation number 928122506. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Selskapets formål er å kjøpe og eie 100 % av aksjene i Glostrup Retail Park Holding ApS, som igjen skal eie 100 % av aksjene i TBD ("Target Company"), som eier eiendommen Hovedvejen 197-209 / Tjalfesvej 1-19 i Glostrup, Danmark, og gjennom dette eierskap drifte eiendommen, samt hva som hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −403,000
Equity
NOK 205.7m
Est. value
NOK 207.2m

Financial health · 2025

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

Who owns GLOSTRUP RETAIL PARK AS?

SWISS LIFE REF NORDIC 2020 AS
GLOSTRUP RETAIL PARK AS
· NOK −403,000 profit

GLOSTRUP RETAIL PARK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GLOSTRUP RETAIL PARK AS

Who owns GLOSTRUP RETAIL PARK AS?

SWISS LIFE REF NORDIC 2020 AS is the largest registered owner, with 99.2%.

Where is GLOSTRUP RETAIL PARK AS based?

GLOSTRUP RETAIL PARK AS has its business address in Oslo.

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.