biztrac. BETA
COMPANY REGISTER PROFILE
932949466 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

HG VENTURES AS

Org. no. 932949466 Limited company (AS) Bergen Incorporated 2024 Active
Revenue 2025 NOK 0
Operating profit NOK −11
Equity NOK 1.2m
Incorporated 2024
Share capital NOK 60,000

Signals

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

HG VENTURES AS is registered as a limited company in Bergen, Vestland with organisation number 932949466. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap med formål å eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11
▲ +100 %
Equity
NOK 1.2m
▼ −0 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
25.78
Very good
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
96.3%
Very good
Equity as a share of total capital

Who owns HG VENTURES AS?

HG VENTURES AS
NOK 0 rev. · NOK −11 profit

HG VENTURES AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Which companies does HG VENTURES AS own?

HG VENTURES AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about HG VENTURES AS

Who owns HG VENTURES AS?

Herman Granerud is the largest registered owner, with 100.0%.

What is the revenue of HG VENTURES AS?

HG VENTURES AS had revenue of NOK 0 in 2025.

Where is HG VENTURES AS based?

HG VENTURES AS has its business address in Bergen.

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.