BIZTRAC BETA
Rental and operating of own or leased real estate

KONGSSENTERET HOLDING AS

Org. no. 830215832 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −489,000
Equity NOK 56.2m
Incorporated 2022
Share capital NOK 60,000

Signals

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

KONGSSENTERET HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 830215832. 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 60,000, divided into 1000 shares. The company's stated purpose is: “Drive virksomhet innenfor utvikling, forvalting og investering i andre selskaper, samt investering i fast eiendom og andre formuesgoder og alt som står i forbindelse med de forannevnte virksomheter.”.

Key figures · 2024

Operating profit
NOK −489,000
Equity
NOK 56.2m
Est. value
NOK 42.4m

Financial health · 2024

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

Who owns KONGSSENTERET HOLDING AS?

AURIS AS
KONGSSENTERET HOLDING AS
· NOK −489,000 profit

KONGSSENTERET HOLDING AS has 8 registered shareholders:

All shareholders and roles →

Which companies does KONGSSENTERET HOLDING AS own?

KONGSSENTERET HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KONGSSENTERET HOLDING AS

Who owns KONGSSENTERET HOLDING AS?

AURIS AS is the largest registered owner, with 25.0%.

Where is KONGSSENTERET HOLDING AS based?

KONGSSENTERET 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 15.06.2026.

Report a problem

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