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

RUBICON HEALTHCARE SPV I AS

Org. no. 935893097 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −2.2m
Equity NOK 61.7m
Incorporated 2025
Share capital NOK 6.4m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,2 mill kr).

RUBICON HEALTHCARE SPV I AS is registered as a limited company in Oslo, Oslo with organisation number 935893097. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2025. Registered share capital is NOK 6.4m, divided into 64010103 shares. The company's stated purpose is: “Å være et alternativt investeringsfond som skal investere direkte eller indirekte, alene eller sammen med andre, eller investere i andre finansielle instrumenter som direkte eller indirekte kan være egnet til å gi selskapet tilgang til investeringer, samt alt som står i forbindelse med dette.”.

Former names: NFH 250718 AS

Key figures · 2025

Operating profit
NOK −2.2m
Equity
NOK 61.7m
Est. value
NOK 56.3m

Financial health · 2025

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

Who owns RUBICON HEALTHCARE SPV I AS?

RUBICON HEALTHCARE SPV I AS
· NOK −2.2m profit

RUBICON HEALTHCARE SPV I AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RUBICON HEALTHCARE SPV I AS

Who owns RUBICON HEALTHCARE SPV I AS?

RUBICON HEALTHCARE PARTNERS AS is the largest registered owner, with 100.0%.

Where is RUBICON HEALTHCARE SPV I AS based?

RUBICON HEALTHCARE SPV I 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 03.10.2026.

Report a problem

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