NORWAY · WELLBORES · NPDID 256
2/4-12
Exploration · Wildcat · P&A · Dry · Phillips Petroleum Company Norway · PL 018
Core 5
Core 5 of 2/4-12 was cut from 11,040 to 11,100 ft, 60 ft in the Tor Fm. The Directorate lists core samples from it as available.
- 60
- ft cored · 11,040 to 11,100
- 5
- log runs across it
SODIR FACTPAGES · PLACED BY DEPTH IN THIS WELLBORE · CORE FILED IN FEET, COMPARED AS 3,365 TO 3,383.3 M
Down the core
TOP OF THE CORE AT THE TOP · TAP A MARK FOR WHAT IT IS
The Directorate has no photographs, thin sections, core-derived slides, or tests on file inside this core's interval. The well's core reports, where there are any, are below.
What it was cut through
| Unit | From, m | To, m | Core in it, m |
|---|---|---|---|
| Tor Fm | 3,365 | 3,383 | 18 |
Logs run across it
5 RUNS COVERING PART OF THE INTERVAL
- IESinduction electrical survey1,212 to 3,383 m
- BHC-Cborehole-compensated sonic1,214 to 3,382 m
- CDM AP PP3,061 to 3,382 m
- DIRdirectional survey3,061 to 3,382 m
- FDC CNLcompensated formation density · compensated neutron log3,061 to 3,382 m
Core and petrography reports on file for the well
- Core Lithological Descriptionpdf · 620 KB
Seeing the core itself
The core is held by the Norwegian Offshore Directorate in its Geobank, which has rooms for viewing and sampling by booking.
About this data
Norwegian Offshore Directorate (Sodir) FactPages, mirrored nightly and used under the Norwegian Licence for Open Government Data (NLOD). The Directorate files a core as an interval and nothing against it. Everything else on this page is on file for the wellbore and is shown here because its depth falls inside the core's interval: photographs by the interval in their title, thin sections and slides by their depth, tests and logs by overlap, units by this wellbore's own tops. Core depths are driller's depths, so a mark at the very edge can belong to the neighboring core. Reports are filed for the well, not for one core.
Developers: this page as JSON is GET /v1/data/norway/wells/256/cores/5, documented in the API reference.