BIZTRAC BETA
COMPANY REGISTER PROFILE
882295982 ORG. NO. 9 SECTIONS
Active UPDATED 02.09.2026
Activities of business and employers membership organisations

GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON

Org. no. 882295982 Association/club/organisation (FLI) Oslo Incorporated 2000 Active
Ownership graph ↗
Incorporated 2000

GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON is registered as a association/club/organisation in Oslo, Oslo with organisation number 882295982. The business is classified under activities of business and employers membership organisations (NACE 94.110). The company was incorporated in 2000. The company's stated purpose is: “Landsdekkende organisasjon for bedrifter i media- og kommunikasjonsbransjen.”.

Former names: VISUELL KOMMUNIKASJON NORGE BA, NHO GRAFISK

Who owns GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON?

No shareholders are registered for GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON

Who is the general manager of GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON?

Robert Wright is registered as general manager of GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON.

Where is GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON based?

GRAFISK BRANSJEFORENING - PRINT OG KOMMUNIKASJON has its business address in Oslo.

Property

Business address Middelthuns gate 27, 0368 Oslo
Cadastral unit 301-215/233/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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