NORWAY · WELLBORES · NPDID 8124
16/1-27
Exploration · Appraisal · P&A · Oil · Lundin Norway AS · Edvard Grieg · PL 338
Core 2
Core 2 of 16/1-27 was cut from 1,993.1 to 2,000.1 m, 7 m in the Skagerrak Fm. The Directorate lists core samples from it as available.
- 7
- m cored · 1,993.1 to 2,000.1
- 4
- 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
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 |
|---|---|---|---|
| Skagerrak Fm | 1,993.1 | 2,000.1 | 7 |
Logs run across it
4 RUNS COVERING PART OF THE INTERVAL
- FMI MSIPformation micro-imager · modular sonic imaging platform (Sonic Scanner)1,875 to 2,260 m
- MWD - GR PWD RES DIR DEN NEU MAGmeasurement while drilling · gamma ray · pressure while drilling · resistivity · directional survey · density · neutron1,912 to 2,258 m
- MSCTmechanical sidewall coring tool1,952 to 2,114 m
- MDTmodular formation dynamics tester1,963 to 2,239 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/8124/cores/2, documented in the API reference.