BIZTRAC BETA
Other captive investment companies

SLV HOLDING AS

Org. no. 889069112 Limited company (AS) Drammen Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.7m
Equity NOK 168.7m
Incorporated 2005
Share capital NOK 120,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).

SLV HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 889069112. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 120,000, divided into 120 shares. The company's stated purpose is: “Investerings- og holdingsvirksomhet og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.7m
Equity
NOK 168.7m
Est. value
NOK 153.9m

Financial health · 2024

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

Who owns SLV HOLDING AS?

VIBEKE FREDRIKSEN
SLV HOLDING AS
NOK 0 rev. · NOK −1.7m profit

SLV HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SLV HOLDING AS own?

SLV HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SLV HOLDING AS

Who owns SLV HOLDING AS?

VIBEKE FREDRIKSEN is the largest registered owner, with 50.8%.

What is the revenue of SLV HOLDING AS?

SLV HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of SLV HOLDING AS?

Lasse Kjøsterud is registered as general manager of SLV HOLDING AS.

Where is SLV HOLDING AS based?

SLV HOLDING AS has its business address in Drammen.

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.