BIZTRAC BETA
Other captive investment companies

HV. HOLDING AS

Org. no. 918064729 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 22,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

HV. HOLDING AS is registered as a limited company in Haugesund, Rogaland with organisation number 918064729. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å investere i og eie aksjer og andeler i andre selskaper, samt annen virksomhet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 22,000
Est. value
NOK 255,000

Financial health · 2024

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

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

Who owns HV. HOLDING AS?

SIGURD HELGE HOVDA
HV. HOLDING AS
NOK 0 rev. · NOK −2,000 profit

HV. HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HV. HOLDING AS own?

HV. HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HV. HOLDING AS

Who owns HV. HOLDING AS?

SIGURD HELGE HOVDA is the largest registered owner, with 100.0%.

What is the revenue of HV. HOLDING AS?

HV. HOLDING AS had revenue of NOK 0 in 2024.

Where is HV. HOLDING AS based?

HV. HOLDING AS has its business address in Haugesund.

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.