BIZTRAC BETA
COMPANY REGISTER PROFILE
937048580 ORG. NO. 7 SECTIONS
Bankrupt UPDATED 02.09.2026
PRICEMYTOUR AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Other content distribution activities

PRICEMYTOUR AS

Org. no. 937048580 Limited company (AS) Stavanger Incorporated 2026 Bankrupt
Ownership graph ↗
Incorporated 2026
Share capital NOK 30,000

Signals

4 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2026-01-15.
  • Nylig endring 2026-09-05 Konkurs registrert 2026-09-05.

PRICEMYTOUR AS is registered as a limited company in Stavanger, Rogaland with organisation number 937048580. The business is classified under other content distribution activities (NACE 60.390). The company was incorporated in 2026. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drifte websider, investere i, eie og forvalte aksjer og andre eierandeler i selskaper innen reiseliv og reiserelatert virksomhet, samt det som naturlig står i forbindelse med dette.”.

Who owns PRICEMYTOUR AS?

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

Frequently asked questions about PRICEMYTOUR AS

Where is PRICEMYTOUR AS based?

PRICEMYTOUR AS has its business address in Stavanger.

Property

Business address Bakkesvingen 27B, 4019 Stavanger
Cadastral unit 1103-57/1921/0/0
Building Tomannsbolig, vertikal · 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.