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

HAVSTAD EIENDOM 2 AS

Org. no. 937142951 Limited company (AS) Ulstein Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-01-20.

HAVSTAD EIENDOM 2 AS is registered as a limited company in Ulstein, Møre og Romsdal with organisation number 937142951. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen utleie av eiendom og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Who owns HAVSTAD EIENDOM 2 AS?

No shareholders are registered for HAVSTAD EIENDOM 2 AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HAVSTAD EIENDOM 2 AS

Who is the general manager of HAVSTAD EIENDOM 2 AS?

Erlend Førre is registered as general manager of HAVSTAD EIENDOM 2 AS.

Where is HAVSTAD EIENDOM 2 AS based?

HAVSTAD EIENDOM 2 AS has its business address in Ulsteinvik.

Property

Business address Sjøgata 47, 6065 Ulsteinvik
Cadastral unit 1516-8/36/0/0
Building Annen boligbygning (sekundærbolig reindrift) · 1 unit

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