BIZTRAC BETA
COMPANY REGISTER PROFILE
936317162 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

VESTLUNDVEIEN BLOKK G AS

Org. no. 936317162 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,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.

VESTLUNDVEIEN BLOKK G AS is registered as a limited company in Bergen, Vestland with organisation number 936317162. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i og utvikling av fast eiendom, samt det som står i forbindelse med dette.”.

Who owns VESTLUNDVEIEN BLOKK G AS?

VESTLUNDVEIEN BLOKK G AS

VESTLUNDVEIEN BLOKK G AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTLUNDVEIEN BLOKK G AS

Who owns VESTLUNDVEIEN BLOKK G AS?

ALVER BOLIG AS is the largest registered owner, with 100.0%.

Who is the general manager of VESTLUNDVEIEN BLOKK G AS?

Thomas Nesheim is registered as general manager of VESTLUNDVEIEN BLOKK G AS.

Where is VESTLUNDVEIEN BLOKK G AS based?

VESTLUNDVEIEN BLOKK G AS has its business address in Bergen.

Property

Business address Strandgaten 9, 5013 Bergen
Cadastral unit 4601-165/16/0/0
Building Annen forretningsbygning · 1 unit

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