BIZTRAC BETA
Other captive investment companies

SALVEHØLEN HOLDING AS

Org. no. 912692175 Limited company (AS) Grimstad Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −47,000
Equity NOK 31.2m
Incorporated 2013
Share capital NOK 452,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−47k kr).

SALVEHØLEN HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 912692175. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 452,000, divided into 452 shares. The company's stated purpose is: “Å opptre som holdingselskap samt investere i aksjer og andeler og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −47,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −47,000
Equity
NOK 31.2m
Est. value
NOK 28.5m

Financial health · 2024

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

Who owns SALVEHØLEN HOLDING AS?

JENS TVEITE
SALVEHØLEN HOLDING AS
NOK 0 rev. · NOK −47,000 profit

SALVEHØLEN HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SALVEHØLEN HOLDING AS own?

SALVEHØLEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SALVEHØLEN HOLDING AS

Who owns SALVEHØLEN HOLDING AS?

JENS TVEITE is the largest registered owner, with 58.6%.

What is the revenue of SALVEHØLEN HOLDING AS?

SALVEHØLEN HOLDING AS had revenue of NOK 0 in 2024.

Where is SALVEHØLEN HOLDING AS based?

SALVEHØLEN HOLDING AS has its business address in Grimstad.

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.