BIZTRAC BETA
Retail sale of automotive fuel

HEGGE HOLDING AS

Org. no. 996413586 Limited company (AS) Øyer Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −72,000
Equity NOK 3.4m
Incorporated 2010
Share capital NOK 100,000

Signals

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

HEGGE HOLDING AS is registered as a limited company in Øyer, Innlandet with organisation number 996413586. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, kjøpe og selge aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −72,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −72,000
Equity
NOK 3.4m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns HEGGE HOLDING AS?

EISTEIN SVERRE RAABE HEGGE
HEGGE HOLDING AS
NOK 0 rev. · NOK −72,000 profit

HEGGE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEGGE HOLDING AS own?

HEGGE HOLDING AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about HEGGE HOLDING AS

Who owns HEGGE HOLDING AS?

EISTEIN SVERRE RAABE HEGGE is the largest registered owner, with 100.0%.

What is the revenue of HEGGE HOLDING AS?

HEGGE HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of HEGGE HOLDING AS?

Eistein Sverre Raabe Hegge is registered as general manager of HEGGE HOLDING AS.

Where is HEGGE HOLDING AS based?

HEGGE HOLDING AS has its business address in Øyer.

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.