BIZTRAC BETA
Accounting and bookkeeping

HGVIKEN AS

Org. no. 931784471 Limited company (AS) Bergen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 10,000
Operating profit NOK 8,000
Equity NOK −7,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7k kr).

HGVIKEN AS is registered as a limited company in Bergen, Vestland with organisation number 931784471. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjenester innen økonomi og regnskap. Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 10,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 10,000
Operating profit
NOK 8,000
Equity
NOK −7,000
Est. value
NOK 35,000

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-29.6%
Weak
Equity as a share of total capital

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

Who owns HGVIKEN AS?

HELENE GAMST VIKEN
HGVIKEN AS
NOK 10,000 rev. · NOK 8,000 profit

HGVIKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HGVIKEN AS own?

HGVIKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HGVIKEN AS

Who owns HGVIKEN AS?

HELENE GAMST VIKEN is the largest registered owner, with 100.0%.

What is the revenue of HGVIKEN AS?

HGVIKEN AS had revenue of NOK 10,000 in 2025.

Where is HGVIKEN AS based?

HGVIKEN AS has its business address in Loddefjord.

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.