WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-291-02403
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.
15 LOG FILES ON 10 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Barrett W. J. #642-291-32763Liberty, TX · Hughes Oil Operating LLC | 0.22 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 2,704 to 9,039 | Dec 10, 2009run Aug 6, 2008 |
| Barrett W. J. #642-291-32763Liberty, TX · Hughes Oil Operating LLC | 0.22 | SURVEYS CASED HOLETIFF | 8,500 to 8,796 | Dec 7, 2009run Jan 16, 2009 |
| Barrett W. J. Estate #442-291-32523Liberty, TX · Hemco Development LLC | 0.22 | Neutron PorosityTIFFGAMMA RAY DUAL NEUTRON CCL | 6,900 to 8,943 | Feb 28, 2008run Apr 12, 2004 |
| Barrett W J #542-291-32690Liberty, TX · Hughes Oil Operating LLC | 0.23 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 2,700 to 8,986 | Mar 23, 2010run Feb 23, 2007 |
| Wirt Davis #142-291-32554Liberty, TX · Hughes Oil Operating LLC | 0.74 | RESISTIVITYTIFF | 3,214 to 10,052 | Aug 27, 2008run Oct 29, 2004 |
| Holland #142-291-32858Liberty, TX · Gordy Oil Company | 0.84 | NEUTRON/DENSITY POROSITY2 TIFF | 2,651 to 9,596 | Jun 23, 2015run May 21, 2012 |
| Richardson Unit #142-291-32569Liberty, TX · Hughes Oil Operating LLC | 0.89 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 3,245 to 9,230 | Aug 27, 2008run Nov 25, 2004 |
| Barrett #242-291-32712Liberty, TX · Hughes Oil Operating LLC | 0.98 | RESISTIVITYTIFF | 3,534 to 11,498 | Apr 2, 2013run Jul 4, 2007 |
| Barrett #242-291-32712Liberty, TX · Hughes Oil Operating LLC | 0.98 | RESISTIVITYTIFF | 3,534 to 13,224 | Oct 6, 2014run Jul 18, 2007 |
| Taub #142-291-32645Liberty, TX · Hughes Oil Operating LLC | 1.25 | RESISTIVITYTIFF | 3,516 to 12,144 | Jun 25, 2009run May 1, 2006 |
| Barrett #142-291-32608Liberty, TX · Hughes Oil Operating LLC | 1.28 | Acoustic PorosityTIFFARRAY INDUCTION LONG SPACED SONIC FINAL COMPOSITE | 3,445 to 9,275 | Jan 10, 2007run Aug 13, 2005 |
| Humphreys #342-291-32601Liberty, TX · Caskids Operating Company | 1.30 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 3,528 to 9,760 | Oct 2, 2008run Jul 8, 2005 |
| Humphreys #342-291-32601Liberty, TX · Caskids Operating Company | 1.30 | NEUTRON/DENSITY POROSITYTIFF | 3,528 to 9,760 | May 15, 2009run Jul 8, 2005 |
| Humphreys #342-291-32601Liberty, TX · Caskids Operating Company | 1.30 | SURVEYS CASED HOLETIFF | 8,000 to 9,586 | May 15, 2009run Jul 28, 2005 |
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.