BIZTRAC BETA
COMPANY REGISTER PROFILE
837608902 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Joinery installation

PROBENK AS

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

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-04-08.

PROBENK AS is registered as a limited company in Malvik, Trøndelag with organisation number 837608902. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Leverer montering og spesialtilpasning av kjøkken, benkeplater og innredningsløsninger til privat- og bedriftsmarkedet i Trondheim og Trøndelag. Tjenestene utføres på oppdragsbasis med fokus på effektiv gjennomføring og høy kvalitet. Inntekter kommer fra timebaserte oppdrag, fastprisprosjekter samt påslag på materiell og logistikk.”.

Who owns PROBENK AS?

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

Frequently asked questions about PROBENK AS

Who is the general manager of PROBENK AS?

Martin Nubdal is registered as general manager of PROBENK AS.

Where is PROBENK AS based?

PROBENK AS has its business address in Saksvik.

Property

Business address Johan Ellingsens veg 18A, 7562 Saksvik
Cadastral unit 5031-1/686/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

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