15/9-16
Exploration · Appraisal · P&A · Gas/condensate · Den norske stats oljeselskap a.s · Sleipner Øst · PL 046
Core 5
Core 5 of 15/9-16 was cut from 2,441 to 2,460 m, 19 m in the Heimdal Fm. The Directorate lists core samples from it as available.
- 19
- m cored · 2,441 to 2,460
- 4
- photographs
- 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 |
|---|---|---|---|
| Heimdal Fm | 2,441 | 2,460 | 19 |
Logs run across it
7 RUNS COVERING PART OF THE INTERVAL
- CBL VDL GRcement bond log · variable density log · gamma ray108 to 2,635 m
- ISF SONinduction spherically focused log · sonic110 to 2,651 m
- VELOCITYvelocity (check-shot) survey300 to 3,116 m
- HDT CYBERDIPhigh-resolution dipmeter · computed dipmeter1,152 to 3,117 m
- LDT CNL GRlitho-density tool · compensated neutron log · gamma ray1,152 to 3,115 m
- DLL MSFLdual laterolog · micro-spherically focused log2,250 to 2,550 m
- RFTrepeat formation tester2,307 to 2,484 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/79/cores/5, documented in the API reference.