WELL LOGS · UNITED STATES · ONE ROW PER LOG

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

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

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Cook -a- Sec. 118 #23W42-417-01246Shackelford, TX · Stasney Well Service LLC0.12InductionTIFF100 to 1,409Apr 24, 2020
Cook -a- Sec. 118 #19W42-417-01313Shackelford, TX · Stasney Well Service LLC0.18InductionTIFF100 to 1,418Jun 26, 2019
Cook Ranch 111A #4842-417-38430Shackelford, TX · Stasney Well Service LLC0.49InductionTIFF122 to 1,702Jul 2, 2020
Cook Ranch 117D #142-417-20411Shackelford, TX · Stasney Well Service LLC0.81SURVEYS CASED HOLETIFF750 to 1,556Mar 30, 2010run Oct 20, 2008
Cook Ranch 117 #4342-417-39324Shackelford, TX · Stasney Well Service LLC0.95RESISTIVITYTIFF80 to 1,742Mar 3, 2015run Jun 19, 2014
Cook Ranch 117 #4542-417-39660Shackelford, TX · Stasney Well Service LLC1.02InductionTIFF84 to 1,615Mar 12, 2019
Stasney Ranch 140 #1442-417-39681Shackelford, TX · Stasney Well Service LLC1.06InductionTIFF72 to 1,678Mar 17, 2020
Nail J.H. 119 #11742-417-38873Shackelford, TX · Tom-Tom Operating LLC1.13RESISTIVITYTIFF40 to 1,585Feb 5, 2009run Aug 14, 2008
Cook 116S #1542-417-39078Shackelford, TX · Stasney Well Service LLC1.19RESISTIVITYTIFF90 to 3,505Mar 11, 2013run Aug 14, 2010
Nail J.H. 119 #11042-417-38661Shackelford, TX · Tom-Tom Operating LLC1.32ResistivityTIFFDUAL INDUCTION SFL-SP GAMMA RAY100 to 1,465Jul 13, 2007run Feb 1, 2007
Cook W. I. Estates Sec. /139A/ #7A42-417-11355Shackelford, TX · Stasney Well Service LLC1.58Induction2 TIFF1665 to 110 as filedOct 24, 2017
Nail J.H. 119 #11142-417-38662Shackelford, TX · Tom-Tom Operating LLC1.65ResistivityTIFFDUAL INDUCTION SFL-SP GAMMA RAY100 to 1,465Jul 25, 2007run Feb 16, 2007
Nail J.H.119 #107__42-417-38619Shackelford, TX · Synergy Operating Co. LLC1.75ResistivityTIFFDUAL INDUCTION SFL-SP GAMMA RAY100 to 1,563Oct 19, 2006run Aug 23, 2006
Nail J.H. 119 #10642-417-38618Shackelford, TX · Tom-Tom Operating LLC1.78ResistivityTIFFDUAL INDUCTION SFL-SP GAMMA RAY100 to 1,435Apr 17, 2007run Sep 23, 2006
Nail J.H. 119 #11242-417-38668Shackelford, TX · Tom-Tom Operating LLC1.84RESISTIVITYTIFF100 to 1,550Mar 15, 2010run Jul 17, 2007
Cook Ranch 116 #1442-417-38603Shackelford, TX · Stasney H. R. & Sons Ltd.1.89ResistivityTIFFDUAL FOCUSED LOG100 to 1,868Jun 15, 2007run Aug 1, 2006
Cook Ranch 113 #3842-417-38937Shackelford, TX · Stasney Well Service LLC1.93RESISTIVITYTIFF78 to 1,542Sep 4, 2009run Nov 26, 2008

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.