BIZTRAC BETA
COMPANY REGISTER PROFILE
937497296 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Norwegian company

SANDVIK SERVICE-SOLUTIONS AS

Org. no. 937497296 Limited company (AS) Vindafjord 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-09-04 Adresseendring registrert 2026-09-04.

SANDVIK SERVICE-SOLUTIONS AS is registered as a limited company in Vindafjord, Rogaland with organisation number 937497296. The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å drive med annen teknisk konsulentvirksomhet innen industri, anlegg og offshore, herunder mekaniske løsninger, drift, vedlikehold, løfteoperasjoner og utleie av utstyr, samt det som naturlig står i forbindelse med dette.”.

Who owns SANDVIK SERVICE-SOLUTIONS AS?

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

Frequently asked questions about SANDVIK SERVICE-SOLUTIONS AS

Who is the general manager of SANDVIK SERVICE-SOLUTIONS AS?

Per Inge Sandvik is registered as general manager of SANDVIK SERVICE-SOLUTIONS AS.

Where is SANDVIK SERVICE-SOLUTIONS AS based?

SANDVIK SERVICE-SOLUTIONS AS has its business address in Vikedal.

Property

Business address Urabø 9, 5583 Vikedal
Cadastral unit 1160-66/159/0/0
Building Enebolig · 1 unit

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