BIZTRAC BETA
COMPANY REGISTER PROFILE
935496594 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

XAIT HOLDCO AS

Org. no. 935496594 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 550,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-07-20 Adresseendring registrert 2026-07-20.

XAIT HOLDCO AS is registered as a limited company in Oslo, Oslo with organisation number 935496594. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 550,000, divided into 5503694 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper og gjennomføre investeringer og virksomhet i forbindelse med dette.”.

Former names: NFH 250559 AS

Who owns XAIT HOLDCO AS?

XAIT HOLDCO AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does XAIT HOLDCO AS own?

XAIT HOLDCO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about XAIT HOLDCO AS

Who owns XAIT HOLDCO AS?

MAIN CAPITAL VIII COÖPERATIEF U.A. is the largest registered owner, with 47.6%.

Who is the general manager of XAIT HOLDCO AS?

Eirik Gudmundsen is registered as general manager of XAIT HOLDCO AS.

Where is XAIT HOLDCO AS based?

XAIT HOLDCO AS has its business address in Oslo.

Property

Business address c/o Nytt Foretak AS Tjuvholmen allé 1, 0252 Oslo
Cadastral unit 301-210/37/0/0
Building Kontor- og administrasjonsbygning, rådhus · 9 units

398 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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