BIZTRAC BETA
COMPANY REGISTER PROFILE
937278640 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Beverage serving activities

ROCK IN DRIFT AS

Org. no. 937278640 Limited company (AS) Oslo Incorporated 2026 Active
Ownership graph ↗
Incorporated 2026
Employees 17
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-06-15 Adresseendring registrert 2026-06-15.

ROCK IN DRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 937278640. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2026 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drift av restaurant, bar, pub med eller uten musikkfremføring i egne eller leide lokaler.Drift av restaurant, bar, pub med eller uten musikkfremføring i egne eller leide lokaler.”.

Who owns ROCK IN DRIFT AS?

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

Frequently asked questions about ROCK IN DRIFT AS

Who is the general manager of ROCK IN DRIFT AS?

Erman Bora Atabay is registered as general manager of ROCK IN DRIFT AS.

Where is ROCK IN DRIFT AS based?

ROCK IN DRIFT AS has its business address in Oslo.

Property

Business address Kristian IVs gate 12, 0164 Oslo
Cadastral unit 301-209/173/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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