BIZTRAC BETA
COMPANY REGISTER PROFILE
937072082 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SÖDERBERG & PARTNERS BUSKERUD AS

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

Signals

3 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-01-07.
  • Nylig endring 2026-05-07 Adresseendring registrert 2026-05-07.

SÖDERBERG & PARTNERS BUSKERUD AS is registered as a limited company in Drammen, Buskerud with organisation number 937072082. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forsikringsmegling, samt virksomhet som står i forbindelse med dette.”.

Former names: S&P G AS

Who owns SÖDERBERG & PARTNERS BUSKERUD AS?

No shareholders are registered for SÖDERBERG & PARTNERS BUSKERUD AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SÖDERBERG & PARTNERS BUSKERUD AS

Who is the general manager of SÖDERBERG & PARTNERS BUSKERUD AS?

Kjetil Nilsen is registered as general manager of SÖDERBERG & PARTNERS BUSKERUD AS.

Where is SÖDERBERG & PARTNERS BUSKERUD AS based?

SÖDERBERG & PARTNERS BUSKERUD AS has its business address in Drammen.

Property

Business address Strømsø torg 9, 3044 Drammen
Cadastral unit 3301-110/539/0/0
Building Kontor- og administrasjonsbygning, rådhus · 2 units

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