BIZTRAC BETA
Computer consultancy and computer facilities management activities

GULFSTREAM HOLDCO AS

Org. no. 930938637 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −959,000
Equity NOK 2.9bn
Incorporated 2023
Share capital NOK 28.4m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−959k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GULFSTREAM HOLDCO AS is registered as a limited company in Stavanger, Rogaland with organisation number 930938637. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 28.4m, divided into 2844878530 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −959,000
Equity
NOK 2.9bn
Est. value
NOK 5.2bn

Financial health · 2024

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

Who owns GULFSTREAM HOLDCO AS?

INSIGHT LUXEMBOURG XII S. R.L
GULFSTREAM HOLDCO AS
· NOK −959,000 profit

GULFSTREAM HOLDCO AS has 16 registered shareholders:

All shareholders and roles →

Which companies does GULFSTREAM HOLDCO AS own?

GULFSTREAM HOLDCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GULFSTREAM HOLDCO AS

Who owns GULFSTREAM HOLDCO AS?

INSIGHT LUXEMBOURG XII S. R.L is the largest registered owner, with 36.5%.

Where is GULFSTREAM HOLDCO AS based?

GULFSTREAM HOLDCO AS has its business address in Stavanger.

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.