30/9-2
Exploration · Appraisal · Suspended · Oil/gas · Norsk Hydro Produksjon AS · Oseberg · PL 079
Core 2
Core 2 of 30/9-2 was cut from 2,594 to 2,611.4 m, 17.4 m in the Ness Fm. The Directorate lists core samples from it as available.
- 17.4
- m cored · 2,594 to 2,611.4
- 4
- photographs
- 4
- palynology slides made from core
- 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 |
|---|---|---|---|
| Ness Fm | 2,594 | 2,611.4 | 17.3 |
Palynology slides made from core
4 IN THE INTERVAL
Logs run across it
7 RUNS COVERING PART OF THE INTERVAL
- VSPvertical seismic profile1,268 to 2,830 m
- CDL CNL CAL GRcompensated densilog · compensated neutron log · caliper · gamma ray1,479 to 2,828 m
- DIFL LS BHC GRdual induction focused log · borehole-compensated sonic · gamma ray1,482 to 2,830 m
- HDThigh-resolution dipmeter1,900 to 2,826 m
- SWCsidewall cores2,230 to 2,825 m
- FMTformation multi-tester2,305 to 2,765 m
- SPECTRALOG2,550 to 2,790 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/11/cores/2, documented in the API reference.