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

BRAGSTAD EIENDOM AS

Org. no. 937051158 Limited company (AS) Kvinesdal 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-14.

BRAGSTAD EIENDOM AS is registered as a limited company in Kvinesdal, Agder with organisation number 937051158. 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 100 shares. The company's stated purpose is: “Å investere i, eie, utvikle, forvalte, leie ut og omsette fast eiendom, samt drive virksomhet som naturlig står i forbindelse med dette, herunder å investere i andre selskaper og verdipapirer.”.

Who owns BRAGSTAD EIENDOM AS?

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

Frequently asked questions about BRAGSTAD EIENDOM AS

Who is the general manager of BRAGSTAD EIENDOM AS?

Asbjørn Bragstad is registered as general manager of BRAGSTAD EIENDOM AS.

Where is BRAGSTAD EIENDOM AS based?

BRAGSTAD EIENDOM AS has its business address in Kvinesdal.

Property

Business address Urefjellvegen 21, 4480 Kvinesdal
Cadastral unit 4227-100/167/0/0
Building Enebolig m/hybel/sokkelleil. · 1 unit

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