BIZTRAC BETA
Other captive investment companies

ERIK FOSSGÅRD HOLDING AS

Org. no. 915438571 Limited company (AS) Hol Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 12.5m
Incorporated 2015
Share capital NOK 30,000

Signals

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

ERIK FOSSGÅRD HOLDING AS is registered as a limited company in Hol, Buskerud with organisation number 915438571. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Investering i aksjer og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 12.5m
Est. value
NOK 21.2m

Financial health · 2025

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

Who owns ERIK FOSSGÅRD HOLDING AS?

ERIK FOSSGÅRD
ERIK FOSSGÅRD HOLDING AS
NOK 0 rev. · NOK −17,000 profit

ERIK FOSSGÅRD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERIK FOSSGÅRD HOLDING AS own?

ERIK FOSSGÅRD HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ERIK FOSSGÅRD HOLDING AS

Who owns ERIK FOSSGÅRD HOLDING AS?

ERIK FOSSGÅRD is the largest registered owner, with 100.0%.

What is the revenue of ERIK FOSSGÅRD HOLDING AS?

ERIK FOSSGÅRD HOLDING AS had revenue of NOK 0 in 2025.

Where is ERIK FOSSGÅRD HOLDING AS based?

ERIK FOSSGÅRD HOLDING AS has its business address in Geilo.

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.