NORWAY · WELLBORES · NPDID 357
25/2-5
Exploration · Wildcat · P&A · Oil/gas · Elf Petroleum Norge AS · Hugin Satellitter · PL 026
Core 5
Core 5 of 25/2-5 was cut from 3,476 to 3,484.7 m, 8.7 m in the Sleipner Fm. The Directorate lists core samples from it as available.
- 8.7
- m cored · 3,476 to 3,484.7
- 1
- thin section in the interval
- 8
- 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
What it was cut through
| Unit | From, m | To, m | Core in it, m |
|---|---|---|---|
| Sleipner Fm | 3,476 | 3,484.7 | 8.7 |
Thin sections in this interval
1 ON FILE
| Section | Depth | In |
|---|---|---|
| 4370 | 3,484.5 m | Sleipner Fm |
Logs run across it
8 RUNS COVERING PART OF THE INTERVAL
- SS150 to 3,893 m
- ISF GR SLinduction spherically focused log · gamma ray · spectral gamma ray699 to 4,001 m
- CBLcement bond log1,491 to 3,705 m
- HDThigh-resolution dipmeter2,000 to 4,000 m
- ML MLLmicrolog · microlaterolog2,999 to 4,001 m
- GR CLLgamma ray3,202 to 3,705 m
- DLLdual laterolog3,300 to 3,994 m
- FDC CNLcompensated formation density · compensated neutron log3,300 to 4,001 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/357/cores/5, documented in the API reference.