biztrac. BETA
COMPANY REGISTER PROFILE
989164791 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

VESTFOSSEN HOLDING AS

Org. no. 989164791 Limited company (AS) Øvre Eiker Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 239,000
Incorporated 2005
Share capital NOK 100,000

Signals

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

VESTFOSSEN HOLDING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 989164791. 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: “Aksjeinvesteringer og deltagelse i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
▲ +25 %
Equity
NOK 239,000
▼ −3 %
Est. value
NOK 219,000

Financial health · 2025

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

Who owns VESTFOSSEN HOLDING AS?

VESTFOSSEN HOLDING AS has 6 registered shareholders:

All shareholders and roles →

Which companies does VESTFOSSEN HOLDING AS own?

VESTFOSSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VESTFOSSEN HOLDING AS

Who owns VESTFOSSEN HOLDING AS?

Trond Strandsberg is the largest registered owner, with 24.0%.

What is the revenue of VESTFOSSEN HOLDING AS?

VESTFOSSEN HOLDING AS had revenue of NOK 0 in 2025.

Where is VESTFOSSEN HOLDING AS based?

VESTFOSSEN HOLDING AS has its business address in Vestfossen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.