BIZTRAC BETA
Other captive investment companies

EGGEN HOLDING AS

Org. no. 988959111 Limited company (AS) Nord-Aurdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 242,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

EGGEN HOLDING AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 988959111. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet samt alt som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 242,000
Est. value
NOK 787,000

Financial health · 2025

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

Who owns EGGEN HOLDING AS?

BENTE ELISABET EGGEN HAGASETH
EGGEN HOLDING AS
NOK 0 rev. · NOK −18,000 profit

EGGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EGGEN HOLDING AS own?

EGGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EGGEN HOLDING AS

Who owns EGGEN HOLDING AS?

BENTE ELISABET EGGEN HAGASETH is the largest registered owner, with 100.0%.

What is the revenue of EGGEN HOLDING AS?

EGGEN HOLDING AS had revenue of NOK 0 in 2025.

Where is EGGEN HOLDING AS based?

EGGEN HOLDING AS has its business address in Fagernes.

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.