WELL LOGS · UNITED STATES · ONE ROW PER LOG

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

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-82736Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Schkade Farm #342-417-39277Shackelford, TX · Mc Glover LLC0.16RESISTIVITYTIFF50 to 540Mar 11, 2013run Jun 20, 2012
Schkade Farm #142-417-39116Shackelford, TX · Glover Michael C.0.19NEUTRON/DENSITY POROSITYTIFF20 to 532Dec 22, 2010run Sep 29, 2010
Schkade Farm #142-417-39116Shackelford, TX · Glover Michael C.0.19RESISTIVITYTIFF20 to 536Dec 22, 2010run Sep 29, 2010
Schkade Farm #542-417-39440Shackelford, TX · Mc Glover LLC0.21RESISTIVITYTIFF0 to 615Apr 21, 2014run Oct 16, 2013
Schkade Farm #242-417-39179Shackelford, TX · Mc Glover LLC0.21RESISTIVITYTIFF50 to 541Jan 5, 2012run Sep 7, 2011
Schkade #4__42-417-01633Shackelford, TX · Roark & Hooker0.29RESISTIVITYTIFF130 to 2,557May 30, 2012run Jul 28, 1963
Beaty Patsy #342-417-38760Shackelford, TX · Dino Operating LLC0.89RESISTIVITYTIFF50 to 800Nov 4, 2008run Jan 16, 2008
Pittman Laver 572 #1442-417-38891Shackelford, TX · Salty Lime Energy LLC1.26RESISTIVITYTIFF50 to 548Apr 4, 2016run Sep 16, 2008
Diller Virginia #70742-417-38719Shackelford, TX · Crow Ken1.29RESISTIVITYTIFF100 to 1,000Oct 9, 2008run Aug 11, 2007
Diller Virginia #90742-417-38742Shackelford, TX · Crow Ken1.36RESISTIVITYTIFF100 to 943Oct 3, 2008run Sep 8, 2007
Diller Virginia #10542-417-38550Shackelford, TX · Crow Ken1.37RESISTIVITYTIFF50 to 650Dec 6, 2017run Nov 14, 2005
Diller Virginia #30642-417-38591Shackelford, TX · Crow Ken1.47RESISTIVITYTIFF100 to 650Jun 13, 2011run May 12, 2006
Diller Virginia #80742-417-38729Shackelford, TX · Crow Ken1.52RESISTIVITYTIFF100 to 788Mar 15, 2010run Aug 27, 2007
Diller Virginia #2T42-417-39451Shackelford, TX · Crow Ken1.57RESISTIVITYTIFF30 to 557Jan 19, 2015run Dec 27, 2013
Diller Virginia #100842-417-38859Shackelford, TX · Crow Ken1.58RESISTIVITYTIFF40 to 634Jan 23, 2009run Aug 14, 2008
Diller Virginia #110842-417-38860Shackelford, TX · Crow Ken1.66RESISTIVITYTIFF50 to 605Jan 16, 2009run Aug 27, 2008
Diller Virginia #50642-417-38592Shackelford, TX · Crow Ken1.69RESISTIVITYTIFF100 to 613Jul 23, 2008run May 12, 2006
Diller Virginia #100742-417-38741Shackelford, TX · Crow Ken1.76RESISTIVITYTIFF100 to 670May 28, 2009run Oct 17, 2007
T Edington 535 #1HHZ42-417-39613Shackelford, TX · Walkabout Operating LLC1.76NeutronTIFF3,770 to 7,370Nov 15, 2024
Diller Virginia #40642-417-38590Shackelford, TX · Crow Ken1.77NEUTRON POROSITYTIFF100 to 604Aug 2, 2011run May 18, 2006
Diller Virginia #40642-417-38590Shackelford, TX · Crow Ken1.77RESISTIVITYTIFF100 to 604Aug 2, 2011run May 18, 2006
Alexander F. W. #1742-417-39541Shackelford, TX · JNS Production LLC1.94RESISTIVITYTIFF130 to 4,670Apr 30, 2018run Mar 25, 2015

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.