biztrac. BETA
COMPANY REGISTER PROFILE
929119665 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

HJUMS EIENDOM AS

Org. no. 929119665 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK 0
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-07-19 Adresseendring registrert 2026-07-19.

HJUMS EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 929119665. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Kjøp og salg av eiendom. Utleie av egen eller leid fast eiendom. Utvikling og salg av egen fast eiendom ellers.”.

Key figures · 2025

Operating profit
NOK 0

Financial health · 2025

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

Who owns HJUMS EIENDOM AS?

HJUMS EIENDOM AS
· NOK 0 profit

HJUMS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HJUMS EIENDOM AS own?

HJUMS EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

HJUMS EIENDOM AS er morselskap for 3 datterselskaper:

Frequently asked questions about HJUMS EIENDOM AS

Who owns HJUMS EIENDOM AS?

BARAKA INVEST AS is the largest registered owner, with 100.0%.

Who is the general manager of HJUMS EIENDOM AS?

Murtaza Ghazi Aslam is registered as general manager of HJUMS EIENDOM AS.

Where is HJUMS EIENDOM AS based?

HJUMS EIENDOM 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.