BIZTRAC BETA
COMPANY REGISTER PROFILE
937493126 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

GEISSBERG AS

Org. no. 937493126 Limited company (AS) Bamble Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Share capital NOK 60,000

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-03-16.
  • Nylig endring 2026-08-13 Aksjekapital registrert 2026-08-13.

GEISSBERG AS is registered as a limited company in Bamble, Telemark with organisation number 937493126. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2026. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Å eie aksjer og eierandeler i andre selskaper, samt forvalte investeringer og kapital knyttet til disse. Selskapet vil primært fungere som et holdingselskap for investeringer i datterselskaper og andre virksomheter. Virksomheten kan også omfatte strategisk eierskap, kapitalforvaltning, investeringer i aksjer og andre finansielle instrumenter, samt aktiviteter som naturlig hører sammen med dette.”.

Who owns GEISSBERG AS?

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

Frequently asked questions about GEISSBERG AS

Where is GEISSBERG AS based?

GEISSBERG AS has its business address in Stathelle.

Property

Business address Stokkevannveien 10, 3962 Stathelle
Cadastral unit 4012-21/272/0/0
Building Verkstedbygning · 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.