8/3-2
Exploration · Wildcat · P&A · Dry · Den norske stats oljeselskap a.s · PL 071
Core 2
Core 2 of 8/3-2 was cut from 2,389 to 2,397.3 m, 8.3 m in the Bryne Fm. The Directorate lists core samples from it as available.
- 8.3
- m cored · 2,389 to 2,397.3
- 1
- photograph
- 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
1 PHOTO · HOSTED BY THE NORWEGIAN OFFSHORE DIRECTORATE
What it was cut through
| Unit | From, m | To, m | Core in it, m |
|---|---|---|---|
| Bryne Fm | 2,389 | 2,397.3 | 8.3 |
Logs run across it
7 RUNS COVERING PART OF THE INTERVAL
- ISF BHC GRinduction spherically focused log · borehole-compensated sonic · gamma ray163 to 2,656 m
- VELOCITYvelocity (check-shot) survey289 to 2,630 m
- LDL CNL GRlitho-density log · compensated neutron log · gamma ray1,135 to 2,657 m
- HDT CYBERDIPhigh-resolution dipmeter · computed dipmeter1,550 to 2,654 m
- NGS GRnatural gamma ray spectrometry · gamma ray1,550 to 2,647 m
- CST GRsidewall core sample taker · gamma ray1,593 to 2,643 m
- RFT GRrepeat formation tester · gamma ray2,376 to 2,640 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/89/cores/2, documented in the API reference.