BIZTRAC BETA
Rental and operating of own or leased real estate

KLP CITYPASSAGEN AS

Org. no. 914906261 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 52.8m
Operating profit NOK 27.7m
Equity NOK 5.3m
Incorporated 2015
Share capital NOK 300,000

KLP CITYPASSAGEN AS is registered as a limited company in Oslo, Oslo with organisation number 914906261. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Erverve, eie, utvikle og forvalte vanlig omsettelig bolig og kontor/forretningseiendom og annen fast eiendom. Det kan drive virksomhet som fremmer dette formålet. Selskapet kan eie aksjer eller selskapsandeler i selskaper som eier eiendommer som nevnt eller som fremmer selskapets formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 52.8m in revenue and NOK 27.7m in operating profit.

Key figures · 2025

Revenue
NOK 52.8m
Operating profit
NOK 27.7m
Equity
NOK 5.3m
Est. value
NOK 49.9m

Financial health · 2025

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Not satisfactory
Equity as a share of total capital

Who owns KLP CITYPASSAGEN AS?

KLP EIENDOM OSLO HOLDING AS
KLP CITYPASSAGEN AS
NOK 52.8m rev. · NOK 27.7m profit

KLP CITYPASSAGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLP CITYPASSAGEN AS

Who owns KLP CITYPASSAGEN AS?

KLP EIENDOM OSLO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KLP CITYPASSAGEN AS?

KLP CITYPASSAGEN AS had revenue of NOK 52.8m in 2025.

Where is KLP CITYPASSAGEN AS based?

KLP CITYPASSAGEN 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.