BIZTRAC BETA
COMPANY REGISTER PROFILE
935382327 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

X EIENDOMSINVEST AS

Org. no. 935382327 Limited company (AS) Bærum Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 100,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

X EIENDOMSINVEST AS is registered as a limited company in Bærum, Akershus with organisation number 935382327. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg og drift av eiendom, samt annet hva hermed står i forbindelse.”.

Who owns X EIENDOMSINVEST AS?

X EIENDOMSINVEST AS

X EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about X EIENDOMSINVEST AS

Who owns X EIENDOMSINVEST AS?

XOURCE GROUP AS is the largest registered owner, with 100.0%.

Who is the general manager of X EIENDOMSINVEST AS?

Waleed Aftab is registered as general manager of X EIENDOMSINVEST AS.

Where is X EIENDOMSINVEST AS based?

X EIENDOMSINVEST AS has its business address in Fornebu.

Property

Business address Lilleruts vei 6, 1364 Fornebu
Cadastral unit 3201-41/935/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 33 units

7 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.