BIZTRAC BETA
Other captive investment companies

SALUD Y PESETAS AS

Org. no. 989040995 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −29,000
Equity NOK 27.4m
Incorporated 2005
Share capital NOK 1.0m

Signals

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

SALUD Y PESETAS AS is registered as a limited company in Oslo, Oslo with organisation number 989040995. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering og forvaltning av andeler og aksjer, herunder å eie andeler i Backegården DA, og annet som har tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 27.4m
Est. value
NOK 30.2m

Financial health · 2024

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

Who owns SALUD Y PESETAS AS?

JØRGEN TYCHO EVERS SOLHEIM
SALUD Y PESETAS AS
NOK 0 rev. · NOK −29,000 profit

SALUD Y PESETAS AS has 8 registered shareholders:

All shareholders and roles →

Which companies does SALUD Y PESETAS AS own?

SALUD Y PESETAS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SALUD Y PESETAS AS

Who owns SALUD Y PESETAS AS?

JØRGEN TYCHO EVERS SOLHEIM is the largest registered owner, with 24.8%.

What is the revenue of SALUD Y PESETAS AS?

SALUD Y PESETAS AS had revenue of NOK 0 in 2024.

Where is SALUD Y PESETAS AS based?

SALUD Y PESETAS AS has its business address in Oslo.

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.