BIZTRAC BETA
Other captive investment companies

HINVEST AS

Org. no. 989163396 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −91,000
Equity NOK 49.1m
Incorporated 2005
Share capital NOK 100,000

Signals

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

HINVEST AS is registered as a limited company in Oslo, Oslo with organisation number 989163396. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forvalte verdier i form av aksjer og andre selskapsandeler, fondsandeler og andre verdipapirer, samt realaktiva som fast eiendom mv. Selskapet har også som formål å drive administrasjon og rådgivning for virksomheter som selskapet har eierandeler i.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −91,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −91,000
Equity
NOK 49.1m
Est. value
NOK 55.6m

Financial health · 2024

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

Who owns HINVEST AS?

JØRGEN JOHAN HAGA
HINVEST AS
NOK 0 rev. · NOK −91,000 profit

HINVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HINVEST AS own?

HINVEST AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about HINVEST AS

Who owns HINVEST AS?

JØRGEN JOHAN HAGA is the largest registered owner, with 100.0%.

What is the revenue of HINVEST AS?

HINVEST AS had revenue of NOK 0 in 2024.

Where is HINVEST AS based?

HINVEST 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.