biztrac. BETA
COMPANY REGISTER PROFILE
935249457 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

HV INVEST SAMPI AS

Org. no. 935249457 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −85,000
Equity NOK 274.7m
Incorporated 2025
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−85k kr).

HV INVEST SAMPI AS is registered as a limited company in Stavanger, Rogaland with organisation number 935249457. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 33,000, divided into 3000 shares. The company's stated purpose is: “Å investere i og eie aksjer, finansielle instrumenter og andeler i andre selskaper både ved egenkapital og gjeld, samt annen virksomhet som står naturlig i forbindelse med dette.”.

Former names: NFH 250309 AS

Key figures · 2025

Operating profit
NOK −85,000
Equity
NOK 274.7m
Est. value
NOK 322.8m

Financial health · 2025

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
96.9%
Very good
Equity as a share of total capital

Who owns HV INVEST SAMPI AS?

HITECVISION VII L.P. GG
HITECVISION NORTH SEA OPPORTUNITY F GG
HV INVEST SAMPI AS
· NOK −85,000 profit

HV INVEST SAMPI AS has 2 registered shareholders:

  • HITECVISION VII L.P. 64.9%
  • HITECVISION NORTH SEA OPPORTUNITY F 35.1%
All shareholders and roles →

Which companies does HV INVEST SAMPI AS own?

HV INVEST SAMPI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HV INVEST SAMPI AS

Who owns HV INVEST SAMPI AS?

HITECVISION VII L.P. is the largest registered owner, with 64.9%.

Where is HV INVEST SAMPI AS based?

HV INVEST SAMPI AS has its business address in Stavanger.

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.