WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-417-81111

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-417-81111Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Bradford a #7A42-417-39508Shackelford, TX · Tabor Creek Oil Company1.15DensityTIFF50 to 843Sep 18, 2018
Bradford a #6A42-417-39507Shackelford, TX · Tabor Creek Oil Company1.17DensityTIFF50 to 829Sep 18, 2018
Bradford a #3A42-417-39172Shackelford, TX · Guy Julaine1.18RESISTIVITYTIFF50 to 852Jan 5, 2012run Apr 5, 2011
Bradford a #2A42-417-39061Shackelford, TX · Tabor Creek Oil Company1.23RESISTIVITYTIFF50 to 875Jun 15, 2010run Mar 9, 2010
Bradford a #1A42-417-39001Shackelford, TX · Tabor Creek Oil Company1.24RESISTIVITYTIFF50 to 875Mar 15, 2010run Aug 12, 2009
Bradford a #5A42-417-39506Shackelford, TX · Tabor Creek Oil Company1.30DensityTIFF400 to 843Sep 18, 2018
Bradford a #4A42-417-39240Shackelford, TX · Tabor Creek Oil Company1.41RESISTIVITYTIFF660 to 1,224Apr 30, 2012run Dec 14, 2011
Bradford B #10B42-417-39548Shackelford, TX · Tabor Creek Oil Company1.41DensityTIFF50 to 856Sep 20, 2018
V. A. & A. W. Powers #442-417-38774Shackelford, TX · TAM2 Squared Energy Services LLC1.44RESISTIVITYTIFF107 to 1,448Jun 4, 2009run Jan 28, 2008
Bradford B #1B42-417-39002Shackelford, TX · Tabor Creek Oil Company1.44NEUTRON/DENSITY POROSITYTIFF50 to 840Feb 24, 2010run Aug 15, 2009
Bradford B #2B42-417-39060Shackelford, TX · Tabor Creek Oil Company1.51RESISTIVITYTIFF80 to 876Jul 5, 2010run Mar 11, 2010
Bradford B #5B42-417-39510Shackelford, TX · Tabor Creek Oil Company1.52DensityTIFF90 to 836Sep 20, 2018
Bradford B #342-417-39171Shackelford, TX · Guy Julaine1.54RESISTIVITYTIFF25 to 813Jan 5, 2012run Apr 20, 2011
Bradford B #6B42-417-39504Shackelford, TX · Tabor Creek Oil Company1.57NeutronTIFF1 to 828Sep 21, 2018
Leech Glen et al #842-417-39270Shackelford, TX · Sanchez Basin Resources LLC1.58RESISTIVITYTIFF50 to 897Jan 5, 2018run Apr 23, 2012
Bradford B #7B42-417-39511Shackelford, TX · Tabor Creek Oil Company1.61DensityTIFF50 to 835Sep 20, 2018
Sanders James #742-417-38809Shackelford, TX · TAM2 Squared Energy Services LLC1.62RESISTIVITYTIFF100 to 963Nov 4, 2008run Apr 9, 2008
Bradford B #1342-417-39536Shackelford, TX · Cegx of Texas LLC1.62NEUTRON/DENSITY POROSITYTIFF20 to 876Jul 28, 2016run Dec 4, 2014
Bradford B #8B42-417-39512Shackelford, TX · Cegx of Texas LLC1.78RESISTIVITYTIFF100 to 830Oct 3, 2016run Dec 19, 2014

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.