BIZTRAC BETA
Rental and operating of own or leased real estate

HJEMMEL STAVANGER AIRPORT HOTEL AS

Org. no. 958364032 Limited company (AS) Oslo Incorporated 1990 Active
Ownership graph ↗
Equity NOK 77,000
Incorporated 1990
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HJEMMEL STAVANGER AIRPORT HOTEL AS is registered as a limited company in Oslo, Oslo with organisation number 958364032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Selskapets formål er å 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.”.

Key figures · 2025

Equity
NOK 77,000
Est. value
NOK 60,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HJEMMEL STAVANGER AIRPORT HOTEL AS?

KLP EIENDOM OSLO HOLDING AS
HJEMMEL STAVANGER AIRPORT HOTEL AS

HJEMMEL STAVANGER AIRPORT HOTEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJEMMEL STAVANGER AIRPORT HOTEL AS

Who owns HJEMMEL STAVANGER AIRPORT HOTEL AS?

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

Where is HJEMMEL STAVANGER AIRPORT HOTEL AS based?

HJEMMEL STAVANGER AIRPORT HOTEL 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.