BIZTRAC BETA
COMPANY REGISTER PROFILE
938169888 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Manufacture of other builders' carpentry and joinery

VIPROTECH SOLUTIONS AS

Org. no. 938169888 Limited company (AS) Bergen 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-07-10.
  • Nylig endring 2026-08-13 Adresseendring registrert 2026-08-13.

VIPROTECH SOLUTIONS AS is registered as a limited company in Bergen, Vestland with organisation number 938169888. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive utvikling, produksjon, import, eksport og salg av energieffektive byggematerialer, isolasjonsløsninger og tekniske elementer. Selskapet skal også yte konsulent- og rådgivningstjenester og bygningstekniske løsninger.”.

Former names: AFAS 100726-09 AS

Who owns VIPROTECH SOLUTIONS AS?

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

Frequently asked questions about VIPROTECH SOLUTIONS AS

Where is VIPROTECH SOLUTIONS AS based?

VIPROTECH SOLUTIONS AS has its business address in Mjølkeråen.

Property

Business address Toppevegen 89, 5136 Mjølkeråen
Cadastral unit 4601-184/2/0/0
Building Våningshus · 1 unit

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