BIZTRAC BETA
Other captive investment companies

HELGE VIKEN HOLDING AS

Org. no. 919039396 Limited company (AS) Hustadvika Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −42,000
Equity NOK 6.4m
Incorporated 2017
Share capital NOK 31,000

Signals

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

HELGE VIKEN HOLDING AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 919039396. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 31,000, divided into 31200 shares. The company's stated purpose is: “Å eie og forvalte aksjer og andeler samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −42,000
Equity
NOK 6.4m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns HELGE VIKEN HOLDING AS?

AUD INGER VIKEN
HELGE VIKEN HOLDING AS
NOK 0 rev. · NOK −42,000 profit

HELGE VIKEN HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does HELGE VIKEN HOLDING AS own?

HELGE VIKEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HELGE VIKEN HOLDING AS

Who owns HELGE VIKEN HOLDING AS?

AUD INGER VIKEN is the largest registered owner, with 76.3%.

What is the revenue of HELGE VIKEN HOLDING AS?

HELGE VIKEN HOLDING AS had revenue of NOK 0 in 2025.

Where is HELGE VIKEN HOLDING AS based?

HELGE VIKEN HOLDING AS has its business address in Bud.

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.