BIZTRAC BETA
Computer consultancy and computer facilities management activities

HKH INVEST AS

Org. no. 928585123 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 1.6m
Incorporated 2021
Share capital NOK 30,000

Signals

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

HKH INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 928585123. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 150 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andre verdipapirer. Deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 1.6m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns HKH INVEST AS?

HERMAN KVISETH HALVORSEN
HKH INVEST AS
NOK 0 rev. · NOK −9,000 profit

HKH INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HKH INVEST AS own?

HKH INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

HKH INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about HKH INVEST AS

Who owns HKH INVEST AS?

HERMAN KVISETH HALVORSEN is the largest registered owner, with 100.0%.

What is the revenue of HKH INVEST AS?

HKH INVEST AS had revenue of NOK 0 in 2024.

Where is HKH INVEST AS based?

HKH INVEST 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.