biztrac. BETA
COMPANY REGISTER PROFILE
815056302 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

CITYCON HOLDING AS

Org. no. 815056302 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −1.3m
Equity NOK 4.2bn
Incorporated 2015
Share capital NOK 1.1bn

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,3 mill kr).

CITYCON HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 815056302. 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 1.1bn, divided into 10000000 shares. The company's stated purpose is: “Eie og forvalte eiendom, direkte eller indirekte gjennom deltakelse i andre selskaper.”.

Former names: STARTFASE 733 AS, CITYCON NORWAY AS

Key figures · 2025

Operating profit
NOK −1.3m
▼ −99 %
Equity
NOK 4.2bn
▲ +1 %
Est. value
NOK 3.0bn

Financial health · 2025

Liquidity
3.95
Very good
Current assets ÷ current liabilities
Profitability
4.1%
Weak
Return on total assets
Solidity
37.9%
Good
Equity as a share of total capital

Who owns CITYCON HOLDING AS?

CITYCON OYJ FI
CITYCON HOLDING AS
· NOK −1.3m profit

CITYCON HOLDING AS has 1 registered shareholder:

  • CITYCON OYJ 100.0%
All shareholders and roles →

Which companies does CITYCON HOLDING AS own?

CITYCON HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CITYCON HOLDING AS

Who owns CITYCON HOLDING AS?

CITYCON OYJ is the largest registered owner, with 100.0%.

Who is the general manager of CITYCON HOLDING AS?

Ondrej Jirák is registered as general manager of CITYCON HOLDING AS.

Where is CITYCON HOLDING AS based?

CITYCON HOLDING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.