BIZTRAC BETA
COMPANY REGISTER PROFILE
936723667 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

DEEP SEA BERGEN DRILLING AS

Org. no. 936723667 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.
  • Nystiftet selskap Selskapet ble stiftet 2025-11-21.

DEEP SEA BERGEN DRILLING AS is registered as a limited company in Bergen, Vestland with organisation number 936723667. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift og utleie av plattform for oljeboring og tilknyttet virksomhet.”.

Who owns DEEP SEA BERGEN DRILLING AS?

DEEP SEA BERGEN DRILLING AS

DEEP SEA BERGEN DRILLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEEP SEA BERGEN DRILLING AS

Who owns DEEP SEA BERGEN DRILLING AS?

ODFJELL DRILLING MALTA LTD is the largest registered owner, with 100.0%.

Who is the general manager of DEEP SEA BERGEN DRILLING AS?

Jakob Korsgaard is registered as general manager of DEEP SEA BERGEN DRILLING AS.

Where is DEEP SEA BERGEN DRILLING AS based?

DEEP SEA BERGEN DRILLING AS has its business address in Kokstad.

Property

Business address Kokstadflaten 35, 5257 Kokstad
Cadastral unit 4601-111/171/0/0
Building Annen kontorbygning · 1 unit

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