BIZTRAC BETA
Wholesale of other household goods

F SALVESEN HOLDING AS

Org. no. 994344218 Limited company (AS) Kristiansand Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 122,000
Incorporated 2009
Share capital NOK 100,000

Signals

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

F SALVESEN HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 994344218. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Investering, forvaltning og finansiering av selskap gjennom aksje-eie og utlån, samt annet som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −8,000
Equity
NOK 122,000
Est. value
NOK 58,000

Financial health · 2025

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

Who owns F SALVESEN HOLDING AS?

FRANK ERIK LINDEVIK SALVESEN
F SALVESEN HOLDING AS
· NOK −8,000 profit

F SALVESEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does F SALVESEN HOLDING AS own?

F SALVESEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about F SALVESEN HOLDING AS

Who owns F SALVESEN HOLDING AS?

FRANK ERIK LINDEVIK SALVESEN is the largest registered owner, with 100.0%.

Who is the general manager of F SALVESEN HOLDING AS?

Frank Erik Lindevik Salvesen is registered as general manager of F SALVESEN HOLDING AS.

Where is F SALVESEN HOLDING AS based?

F SALVESEN HOLDING AS has its business address in Flekkerøy.

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.