NORWAY · WELLBORES · NPDID 218
15/9-7
Exploration · Appraisal · P&A · Gas/condensate · Den norske stats oljeselskap a.s · Sleipner Vest · PL 046
Core 11
Core 11 of 15/9-7 was cut from 3,643 to 3,653 m, 10 m in the Hugin Fm. The Directorate lists core samples from it as available.
- 10
- m cored · 3,643 to 3,653
- 4
- photographs
- 4
- palynology slides made from core
- 7
- log runs across it
SODIR FACTPAGES · PLACED BY DEPTH IN THIS WELLBORE
Down the core
TOP OF THE CORE AT THE TOP · TAP A MARK FOR WHAT IT IS
Photographs of this core
4 PHOTOS · HOSTED BY THE NORWEGIAN OFFSHORE DIRECTORATE
What it was cut through
| Unit | From, m | To, m | Core in it, m |
|---|---|---|---|
| Hugin Fm | 3,643 | 3,653 | 10 |
Palynology slides made from core
4 IN THE INTERVAL
Logs run across it
7 RUNS COVERING PART OF THE INTERVAL
- VELOCITYvelocity (check-shot) survey181 to 3,777 m
- CBLcement bond log425 to 3,656 m
- ISF SONinduction spherically focused log · sonic449 to 3,777 m
- CDM AP2,821 to 3,780 m
- CDM2,827 to 3,778 m
- FDC CNLcompensated formation density · compensated neutron log2,827 to 3,779 m
- DLL MSFLdual laterolog · micro-spherically focused log3,475 to 3,778 m
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/218/cores/11, documented in the API reference.