Pelican AS holds no active production licence on the Norwegian shelf today.
- 0
- active licences held
- 0
- operated
- 0
- fields operated
- 0
- mill Sm³ o.e. from operated fields, last 12 reported
- 0
- wellbores drilled as operator
- 0
- of them with cores on file
SODIR FACTPAGES · AS REGISTERED TODAY
In the Petroleum Register
LATEST 5 OF 6 MESSAGES NAMING IT · AS FILED, IN NORWEGIAN
The Petroleum Register is Norway's public record of rights in production licences. Every transfer of a share, change of operator, mortgage, extension, and lapse is entered there with its date. The Directorate publishes it in Norwegian only, so each entry is shown in its own words with a link to read it in English.
May 8, 2002 · PL 274 · Other messages · DOC 1806
Pelican AS har endret navn til DONG Norge AS.
May 8, 2002 · PL 019 · Other messages · DOC 1803
Pelican AS har endret navn til DONG Norge AS.
May 8, 2002 · PL 048 B · Other messages · DOC 1804
Pelican AS har endret navn til DONG Norge AS.
May 7, 2002 · PL 019 B · Change to licence (kept for historical reasons) · DOC 1799
Petoro AS har overdratt sin 30% andel i tillatelsen til DONG Norge AS (tidligere Pelican AS).
May 7, 2002 · PL 065 · Change to licence (kept for historical reasons) · DOC 1801
Petoro AS har overdratt sin 30% andel i tillatelsen til DONG Norge AS (tidligere Pelican AS).
This company on Sodir FactPages →
About this data
Norwegian Offshore Directorate (Sodir) FactPages, mirrored nightly and used under the Norwegian Licence for Open Government Data (NLOD). Licences and shares are the current rows of each licence's and field's licensee history. Production is the saleable volume of the fields the company operates, the whole field, over the twelve months ending in the latest month any field has reported. Wellbores are those naming the company as drilling operator; a renamed or merged company is a separate record from its predecessor. Register messages are matched on the company's name.
Developers: this page as JSON is GET /v1/data/norway/companies/606, documented in the API reference.