BIZTRAC BETA
Rental and operating of own or leased real estate

CAMPUS GJØVIK AS

Org. no. 921901003 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −189,000
Equity NOK 87.0m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−189k kr).

CAMPUS GJØVIK AS is registered as a limited company in Oslo, Oslo with organisation number 921901003. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Indirekte eller direkte erverve og eie selskapet Studenten Gjøvik AS, org.nr. 983 532 519. Gjennom eierskapet til Studenten Gjøvik AS vil Campus Gjøvik AS indirekte erverve, eie, drifte, leie ut, utvikle, selge, og forestå annen virksomhet som kan knyttes til drift og eierskap av eiendommene gnr. 67. bnr 959, 1263 og 1264 med bygg og anlegg i Gjøvik kommune.”.

Key figures · 2024

Operating profit
NOK −189,000
Equity
NOK 87.0m
Est. value
NOK 60.6m

Financial health · 2024

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

Who owns CAMPUS GJØVIK AS?

UNION REAL ESTATE FUND IV HOLDING AS
CAMPUS GJØVIK AS
· NOK −189,000 profit

CAMPUS GJØVIK AS has 6 registered shareholders:

All shareholders and roles →

Which companies does CAMPUS GJØVIK AS own?

CAMPUS GJØVIK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CAMPUS GJØVIK AS

Who owns CAMPUS GJØVIK AS?

UNION REAL ESTATE FUND IV HOLDING AS is the largest registered owner, with 69.0%.

Where is CAMPUS GJØVIK AS based?

CAMPUS GJØVIK 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.