NORWAY · WELLBORES · NPDID 5551
16/2-3
Exploration · Wildcat · P&A · Oil/gas · Statoil ASA (old) · PL 265
Core 2
Core 2 of 16/2-3 was cut from 1,743 to 1,798.6 m, 55.6 m in the Tor Fm. The Directorate lists core samples from it as available.
- 55.6
- m cored · 1,743 to 1,798.6
- 5
- 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 |
|---|---|---|---|
| Tor Fm | 1,743 | 1,798.6 | 55.6 |
Logs run across it
5 RUNS COVERING PART OF THE INTERVAL
- FMI DSIformation micro-imager · dipole shear sonic imager1,274 to 1,900 m
- ZO VSPvertical seismic profile1,467 to 1,905 m
- CMR PEX HRLAcombinable magnetic resonance · Platform Express (resistivity, density, neutron) · high-resolution laterolog array1,693 to 1,905 m
- MDT PP SAMPLEmodular formation dynamics tester1,716 to 1,864 m
- MDT PP SAMPLEmodular formation dynamics tester1,716 to 1,864 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/5551/cores/2, documented in the API reference.