WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-417-83014
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.
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.
16 LOG FILES ON 15 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| George A. #542-417-39339Shackelford, TX · Rattlesnake Mountain Oil LLC | 1.37 | RESISTIVITYTIFF | 20 to 996 | Jul 4, 2013run Jan 11, 2013 |
| George A. #542-417-39339Shackelford, TX · Rattlesnake Mountain Oil LLC | 1.37 | RESISTIVITYTIFF | 20 to 996 | Aug 26, 2013run Jan 11, 2013 |
| George A. #442-417-39201Shackelford, TX · Rattlesnake Mountain Oil LLC | 1.47 | RESISTIVITYTIFF | 50 to 1,000 | Mar 23, 2012run Sep 26, 2011 |
| Bradford a #3A42-417-39172Shackelford, TX · Guy Julaine | 1.70 | RESISTIVITYTIFF | 50 to 852 | Jan 5, 2012run Apr 5, 2011 |
| Bradford a #7A42-417-39508Shackelford, TX · Tabor Creek Oil Company | 1.71 | DensityTIFF | 50 to 843 | Sep 18, 2018 |
| Bradford a #6A42-417-39507Shackelford, TX · Tabor Creek Oil Company | 1.76 | DensityTIFF | 50 to 829 | Sep 18, 2018 |
| Bradford a #2A42-417-39061Shackelford, TX · Tabor Creek Oil Company | 1.77 | RESISTIVITYTIFF | 50 to 875 | Jun 15, 2010run Mar 9, 2010 |
| Bradford a #1A42-417-39001Shackelford, TX · Tabor Creek Oil Company | 1.82 | RESISTIVITYTIFF | 50 to 875 | Mar 15, 2010run Aug 12, 2009 |
| V. A. & A. W. Powers #442-417-38774Shackelford, TX · TAM2 Squared Energy Services LLC | 1.82 | RESISTIVITYTIFF | 107 to 1,448 | Jun 4, 2009run Jan 28, 2008 |
| J & G #142-417-39494Shackelford, TX · Mc Glover LLC | 1.84 | RESISTIVITYTIFF | 28 to 1,000 | Feb 23, 2015run Jul 23, 2014 |
| Hooker Trust #1342-417-39456Shackelford, TX · Rattlesnake Mountain Oil LLC | 1.84 | RESISTIVITYTIFF | 30 to 975 | Feb 24, 2015run Feb 12, 2014 |
| Hooker Trust #1442-417-39457Shackelford, TX · Rattlesnake Mountain Oil LLC | 1.87 | RESISTIVITYTIFF | 30 to 1,058 | Feb 18, 2015run Jan 29, 2014 |
| Bradford a #4A42-417-39240Shackelford, TX · Tabor Creek Oil Company | 1.88 | RESISTIVITYTIFF | 660 to 1,224 | Apr 30, 2012run Dec 14, 2011 |
| Bradford a #5A42-417-39506Shackelford, TX · Tabor Creek Oil Company | 1.88 | DensityTIFF | 400 to 843 | Sep 18, 2018 |
| Hooker Trust #1142-417-39355Shackelford, TX · Rattlesnake Mountain Oil LLC | 1.93 | RESISTIVITYTIFF | 21 to 1,140 | Feb 23, 2016run Feb 14, 2013 |
| Leech Glen et al #842-417-39270Shackelford, TX · Sanchez Basin Resources LLC | 1.96 | RESISTIVITYTIFF | 50 to 897 | Jan 5, 2018run Apr 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.