NORWAY · WELLBORES · NPDID 6715

16/2-10

Exploration · Appraisal · P&A · Oil · Statoil Petroleum AS · Johan Sverdrup · PL 265

2 documents: reports, logs, and plots →

Everything taken from 16/2-10 that the Directorate has on file, each with its depth and the formation that depth sits in by this wellbore's own tops. Open a core for its photographs, the thin sections and slides cut from it, and the tests across it.

Cores

4 CORES · 69.9 M IN ALL

CoreTopBaseDepth inInPhotosSample available
Core 1 →1,889.51,894.7mÅsgard Fm, Intra Draupne Fm Ss—Yes
Core 2 →1,897.41,912.5mIntra Draupne Fm Ss—Yes
Core 3 →1,912.51,939.6mIntra Draupne Fm Ss, Hugin Fm—Yes
Core 4 →1,939.61,962mHugin Fm—Yes

The core log: every core down the well →Every core from Johan Sverdrup →

Fluid samples

TestFluidFrom, mTo, mInTestedReceivedSample available
MDTOil1,893.5—Intra Draupne Fm SsOct 19, 2011Feb 20, 2012Yes
MDTOil1,927—Hugin FmOct 21, 2011Feb 20, 2012Yes
MDTOil1,935.5—Hugin FmOct 19, 2011Feb 20, 2012Yes

Every fluid sample from Johan Sverdrup →

Cuttings

  • 460 to 2,089 mSample available: yes

Palynology slides

95 ON FILE · 460 TO 1,959

Made from: Ditch cuttings 81, CC 14. Laboratory codes: FUGRO 95.

DepthMade fromLab codeIn
460 mDitch cuttingsFUGRONordland Gp
480 mDitch cuttingsFUGRONordland Gp
500 mDitch cuttingsFUGRONordland Gp
520 mDitch cuttingsFUGRONordland Gp
540 mDitch cuttingsFUGRONordland Gp
560 mDitch cuttingsFUGRONordland Gp
580 mDitch cuttingsFUGRONordland Gp
600 mDitch cuttingsFUGRONordland Gp
620 mDitch cuttingsFUGRONordland Gp
640 mDitch cuttingsFUGRONordland Gp
660 mDitch cuttingsFUGRONordland Gp
680 mDitch cuttingsFUGRONordland Gp
700 mDitch cuttingsFUGRONordland Gp
720 mDitch cuttingsFUGRONordland Gp
740 mDitch cuttingsFUGRONordland Gp
760 mDitch cuttingsFUGRONordland Gp
780 mDitch cuttingsFUGRONordland Gp
800 mDitch cuttingsFUGRONordland Gp
820 mDitch cuttingsFUGROUtsira Fm
840 mDitch cuttingsFUGROUtsira Fm
860 mDitch cuttingsFUGROUtsira Fm
880 mDitch cuttingsFUGROUtsira Fm
900 mDitch cuttingsFUGROUtsira Fm
920 mDitch cuttingsFUGROUtsira Fm
940 mDitch cuttingsFUGROUtsira Fm
960 mDitch cuttingsFUGROUtsira Fm
980 mDitch cuttingsFUGROUtsira Fm
1,000 mDitch cuttingsFUGROUtsira Fm
1,020 mDitch cuttingsFUGROUtsira Fm
1,040 mDitch cuttingsFUGROUtsira Fm
1,060 mDitch cuttingsFUGROHordaland Gp
1,080 mDitch cuttingsFUGROHordaland Gp
1,100 mDitch cuttingsFUGROSkade Fm
1,120 mDitch cuttingsFUGROSkade Fm
1,140 mDitch cuttingsFUGROHordaland Gp
1,160 mDitch cuttingsFUGROHordaland Gp
1,180 mDitch cuttingsFUGROHordaland Gp
1,200 mDitch cuttingsFUGROHordaland Gp
1,220 mDitch cuttingsFUGROHordaland Gp
1,240 mDitch cuttingsFUGROHordaland Gp

Seeing the material itself

The cores, cuttings, and thin sections listed here are physical samples held by the Norwegian Offshore Directorate in its Geobank, which has rooms for viewing and sampling them by booking. There are no images of thin sections or slides online; core photographs are the only pictures the Directorate publishes.

The Directorate's Geobank: viewing and sampling →

About this data

Norwegian Offshore Directorate (Sodir) FactPages, mirrored nightly and used under the Norwegian Licence for Open Government Data (NLOD). Depths are metres along the wellbore from the kelly bushing unless a row gives its own unit; older cores are filed in feet. A core's photographs are the ones whose titled interval overlaps the core's. Reports are placed beside the material they are about by their document type and file name, which is all the Directorate publishes about them. The unit beside a core, sample, test, or slide is the one whose top and base, in this wellbore's own tops, contain that depth; core and test depths are driller's depths, so an interval at a boundary can sit a few metres off. A zero the Directorate files for an unmeasured pressure, density, or temperature is shown as a dash. Availability is the Directorate's flag, not a stock check. Core photographs are links to its own files; Petrora does not hold copies.

Developers: this page as JSON is GET /v1/data/norway/wells/6715, documented in the API reference.