BIZTRAC BETA
COMPANY REGISTER PROFILE
937023197 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Leasing of intellectual property and similar products, except copyrighted works

WATERGUARD INTL AS

Org. no. 937023197 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-02-02.
  • Nylig endring 2026-08-31 Adresseendring registrert 2026-08-31.

WATERGUARD INTL AS is registered as a limited company in Drammen, Buskerud with organisation number 937023197. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie og forvalte rettigheter knyttet til selskapsnavn, varemerker og immaterielle rettigheter, samt virksomhet som naturlig hører inn under dette.”.

Who owns WATERGUARD INTL AS?

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

Group structure

WATERGUARD INTL AS er morselskap for 1 datterselskap:

Frequently asked questions about WATERGUARD INTL AS

Where is WATERGUARD INTL AS based?

WATERGUARD INTL AS has its business address in Drammen.

Property

Business address Bragernes torg 2A, 3017 Drammen
Cadastral unit 3301-114/154/0/0
Building Butikkbygning · 1 unit

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