BIZTRAC BETA
COMPANY REGISTER PROFILE
932096293 ORG. NO. 7 SECTIONS
Compulsory dissolution UPDATED 02.09.2026
SLOTSVIG INVEST AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Uoppgitt

SLOTSVIG INVEST AS

Org. no. 932096293 Limited company (AS) Drammen Incorporated 2023 Compulsory dissolution
Ownership graph ↗
Incorporated 2023
Share capital NOK 60,000

Signals

3 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nylig endring 2026-06-24 Under avvikling registrert 2026-06-24.

SLOTSVIG INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 932096293. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 600 shares. The company's stated purpose is: “Investering i aksjer, andre selskaper og eiendom samt annen relatert virksomhet.”.

Who owns SLOTSVIG INVEST AS?

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

Which companies does SLOTSVIG INVEST AS own?

SLOTSVIG INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SLOTSVIG INVEST AS

Where is SLOTSVIG INVEST AS based?

SLOTSVIG INVEST AS has its business address in Drammen.

Property

Business address Konnerudgata 34, 3045 Drammen
Cadastral unit 3301-110/252/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 12 units

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