NORWAY · WELLBORES · NPDID 4416
30/6-26
Exploration · Wildcat · P&A · Oil/gas · Norsk Hydro Produksjon AS · Oseberg · PL 053
Core 1
Core 1 of 30/6-26 was cut from 2,690 to 2,717.7 m, 27.7 m in the Statfjord Gp. The Directorate lists core samples from it as available.
- 27.7
- m cored · 2,690 to 2,717.7
- 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 |
|---|---|---|---|
| Statfjord Gp | 2,690 | 2,717.7 | 27.7 |
Logs run across it
4 RUNS COVERING PART OF THE INTERVAL
- GR DSI VSPgamma ray · dipole shear sonic imager · vertical seismic profile2,100 to 2,860 m
- MWD - GR RES NEU DEN DIRmeasurement while drilling · gamma ray · resistivity · neutron · density · directional survey2,636 to 2,865 m
- GR MDTgamma ray · modular formation dynamics tester2,669 to 2,857 m
- GR MDTgamma ray · modular formation dynamics tester2,716 to 2,735 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/4416/cores/1, documented in the API reference.