NORWAY · WELLBORES · NPDID 6952

16/2-12

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

2 documents: reports, logs, and plots →

Everything taken from 16/2-12 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 · 58.1 M IN ALL

CoreTopBaseDepth inInPhotosSample available
Core 1 →1,8931,919.4mÅsgard Fm, Intra Draupne Fm Ss—Yes
Core 2 →1,9201,942.8mIntra Draupne Fm Ss, Hugin Fm, Basement—Yes
Core 3 →1,942.81,947.1mBasement—Yes
Core 4 →1,947.11,951.7mBasement—Yes

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

Fluid samples

TestFluidFrom, mTo, mInTestedReceivedSample available
MDTOil1,901.3—Intra Draupne Fm Ss—Jan 16, 2013Yes
MDTOil1,928.3—Intra Draupne Fm Ss—Jan 16, 2013Yes
MDTOil1,940—Basement—Jan 16, 2013Yes

Every fluid sample from Johan Sverdrup →

Cuttings

  • 615 to 2,067 mSample available: yes

Palynology slides

85 ON FILE · 615 TO 1,939.6

Made from: Ditch cuttings 77, Core 8. Laboratory codes: FUGRO 85.

DepthMade fromLab codeIn
615 mDitch cuttingsFUGRONordland Gp
630 mDitch cuttingsFUGRONordland Gp
650 mDitch cuttingsFUGRONordland Gp
670 mDitch cuttingsFUGRONordland Gp
690 mDitch cuttingsFUGRONordland Gp
710 mDitch cuttingsFUGRONordland Gp
730 mDitch cuttingsFUGRONordland Gp
750 mDitch cuttingsFUGRONordland Gp
770 mDitch cuttingsFUGRONordland Gp
790 mDitch cuttingsFUGROUtsira Fm
810 mDitch cuttingsFUGROUtsira Fm
830 mDitch cuttingsFUGROUtsira Fm
850 mDitch cuttingsFUGRONordland Gp
870 mDitch cuttingsFUGRONordland Gp
890 mDitch cuttingsFUGRONordland Gp
910 mDitch cuttingsFUGROSkade Fm
930 mDitch cuttingsFUGROSkade Fm
950 mDitch cuttingsFUGROSkade Fm
970 mDitch cuttingsFUGROSkade Fm
990 mDitch cuttingsFUGROSkade Fm
1,010 mDitch cuttingsFUGROSkade Fm
1,030 mDitch cuttingsFUGROSkade Fm
1,050 mDitch cuttingsFUGROSkade Fm
1,100 mDitch cuttingsFUGROHordaland Gp
1,120 mDitch cuttingsFUGROHordaland Gp
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
1,260 mDitch cuttingsFUGROHordaland Gp
1,280 mDitch cuttingsFUGROHordaland Gp
1,300 mDitch cuttingsFUGROHordaland Gp
1,320 mDitch cuttingsFUGROHordaland Gp
1,340 mDitch cuttingsFUGROHordaland Gp
1,360 mDitch cuttingsFUGROHordaland Gp
1,380 mDitch cuttingsFUGROHordaland Gp
1,400 mDitch cuttingsFUGROHordaland Gp
1,420 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/6952, documented in the API reference.