BIZTRAC BETA
Development of building projects

HJEMOM GRANSTANGEN PARK HUS 19-22 AS

Org. no. 932375532 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 26,000
Incorporated 2023
Share capital NOK 30,000

HJEMOM GRANSTANGEN PARK HUS 19-22 AS is registered as a limited company in Oslo, Oslo with organisation number 932375532. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å drive med utvikling, utleie, eiendomsbesittelse, kjøp og/eller salg av eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 26,000
Est. value
NOK 18,000

Financial health · 2025

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

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

Who owns HJEMOM GRANSTANGEN PARK HUS 19-22 AS?

KARIHAUGEN LOGISTIKKPARK AS
HJEMOM GRANSTANGEN PARK HUS 19-22 AS
NOK 0 rev. · NOK 0 profit

HJEMOM GRANSTANGEN PARK HUS 19-22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJEMOM GRANSTANGEN PARK HUS 19-22 AS

Who owns HJEMOM GRANSTANGEN PARK HUS 19-22 AS?

KARIHAUGEN LOGISTIKKPARK AS is the largest registered owner, with 100.0%.

What is the revenue of HJEMOM GRANSTANGEN PARK HUS 19-22 AS?

HJEMOM GRANSTANGEN PARK HUS 19-22 AS had revenue of NOK 0 in 2025.

Where is HJEMOM GRANSTANGEN PARK HUS 19-22 AS based?

HJEMOM GRANSTANGEN PARK HUS 19-22 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.