Petrora

WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-495-10101

Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-495-10101Clear

Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.

21 LOG FILES ON 16 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Hendricks-M #5B42-495-33501Winkler, TX · Hilcorp Energy Company1.36NEUTRON POROSITYTIFF2,200 to 2,787Aug 25, 2016run Jun 3, 2013
Hendricks-M #5A42-495-33486Winkler, TX · Hilcorp Energy Company1.44RESISTIVITYTIFF2,551 to 2,723Mar 9, 2016run Feb 26, 2013
Hendricks-M #1B42-495-33451Winkler, TX · Hilcorp Energy Company1.47RESISTIVITYTIFF2,200 to 2,660Nov 3, 2015run Nov 29, 2012
Briley #11A42-495-33624Winkler, TX · Hilcorp Energy Company1.48RESISTIVITYTIFF2,435 to 2,785Oct 16, 2017run Oct 11, 2014
Hendricks-M #2B42-495-33488Winkler, TX · Hilcorp Energy Company1.59RESISTIVITYTIFF2,200 to 2,686Mar 9, 2016run Mar 13, 2013
Hendrick Ida T-88-N #1342-495-32959Winkler, TX · Hilcorp Energy Company1.61NEUTRON/DENSITY POROSITYTIFF200 to 2,868Jul 28, 2008run Feb 12, 2005
Hendricks-M #4A42-495-33485Winkler, TX · Hilcorp Energy Company1.61RESISTIVITYTIFF2,190 to 2,690Mar 9, 2016run Mar 6, 2013
Hendricks-M #1A42-495-33415Winkler, TX · Hilcorp Energy Company1.62NEUTRON POROSITYTIFF0 to 2,607Jul 16, 2015run May 15, 2012
Hendricks-M #6B42-495-33498Winkler, TX · Hilcorp Energy Company1.71RESISTIVITYTIFF220 to 2,713Aug 30, 2016run May 22, 2013
Hendricks-M #7B42-495-33503Winkler, TX · Hilcorp Energy Company1.72RESISTIVITYTIFF2,200 to 2,672Mar 7, 2016run Oct 27, 2013
Briley #2A42-495-33448Winkler, TX · Hilcorp Energy Company1.74NEUTRON POROSITYTIFF0 to 2,728Sep 28, 2015run Oct 24, 2012
Hendricks-M #4B42-495-33500Winkler, TX · Hilcorp Energy Company1.74NEUTRON POROSITYTIFF2,200 to 2,760Aug 25, 2016run May 29, 2013
Hendricks-M #15A42-495-33606Winkler, TX · Hilcorp Energy Company1.77OtherTIFF2,300 to 2,730Feb 20, 2018
Hendricks-M #15A42-495-33606Winkler, TX · Hilcorp Energy Company1.77Other3 TIFF2,300 to 2,750Nov 7, 2017
Hendricks-M #15A42-495-33606Winkler, TX · Hilcorp Energy Company1.77RESISTIVITY2 TIFF2,386 to 2,730Mar 21, 2018run Oct 3, 2014
Hendricks T. G. #842-495-33631Winkler, TX · Global Exploration LLC1.81OtherTIFF2,309 to 2,840Oct 30, 2018
Hendricks-M #3B42-495-33490Winkler, TX · Hilcorp Energy Company1.82RESISTIVITYTIFF2,200 to 2,709Mar 15, 2016run Mar 21, 2013
Hendrick Ida #1142-495-33416Winkler, TX · Hilcorp Energy Company1.94NEUTRON POROSITYTIFF0 to 2,456Jun 9, 2015run May 23, 2012

About this data

Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.

Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.