BIZTRAC BETA
COMPANY REGISTER PROFILE
937284462 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Other technical consultancy

OLIMSTAD BRANNRÅDGIVNING AS

Org. no. 937284462 Limited company (AS) Tvedestrand 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-02-23.

OLIMSTAD BRANNRÅDGIVNING AS is registered as a limited company in Tvedestrand, Agder with organisation number 937284462. The business is classified under other technical consultancy (NACE 71.129). 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 ingeniørarbeid og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Who owns OLIMSTAD BRANNRÅDGIVNING AS?

No shareholders are registered for OLIMSTAD BRANNRÅDGIVNING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about OLIMSTAD BRANNRÅDGIVNING AS

Who is the general manager of OLIMSTAD BRANNRÅDGIVNING AS?

Stian Olimstad is registered as general manager of OLIMSTAD BRANNRÅDGIVNING AS.

Where is OLIMSTAD BRANNRÅDGIVNING AS based?

OLIMSTAD BRANNRÅDGIVNING AS has its business address in Tvedestrand.

Property

Business address Langangsveien 104, 4905 Tvedestrand
Cadastral unit 4213-25/46/0/0
Building Enebolig · 1 unit

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