WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-237-81981

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-237-81981Clear

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 15 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Ellis & Dubose -F- #8642-237-32688Jack, TX · DM Backhoe Service0.74Cement BondTIFF0 to 482Feb 7, 2019
Ellis & Dubose -F- #8642-237-32688Jack, TX · DM Backhoe Service0.74Cement BondTIFF482 to 481 as filedOct 9, 2019
Ellis & Dubose -F- #6542-237-40528Jack, TX · DM Backhoe Service0.78Cement BondTIFF0 to 481Apr 28, 2022
Ellis & Dubose -F- #6542-237-40528Jack, TX · DM Backhoe Service0.78Cement BondTIFF0 to 481Jun 26, 2019
Stimpson C. H. -B- Lease #1A42-237-39244Jack, TX · Del Mar Energy Inc.0.88RESISTIVITYTIFF100 to 1,134May 16, 2011run Sep 18, 2008
Ellis B #242-237-38313Jack, TX · Paratus Petroleum LLC0.95Neutron/Density PorosityTIFF3D LITHODENSITY COMPENSATED NEUTRON WITH ML & GR3,450 to 5,006Jun 8, 2007run Oct 4, 1997
Ellis B #242-237-38313Jack, TX · Paratus Petroleum LLC0.95ResistivityTIFFARRAY INDUCTION WITH GAMMA RAY420 to 5,006Jun 8, 2007run Oct 4, 1997
Stimpson C. H. -B- Lease #2A42-237-39225Jack, TX · Del Mar Energy Inc.1.05RESISTIVITYTIFF100 to 1,320May 16, 2011run Sep 11, 2008
Richards Frank #642-237-39298Jack, TX · Paratus Petroleum LLC1.09COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF476 to 5,075Nov 13, 2012run Oct 29, 2009
Richards Frank #542-237-39255Jack, TX · Paratus Petroleum LLC1.12RESISTIVITYTIFF478 to 5,035Jan 6, 2012run Dec 18, 2008
Gillespie D. D. #6C42-237-39414Jack, TX · Lode Holdings LLC1.29NEUTRON POROSITYTIFF189 to 577May 20, 2015run May 18, 2011
Gillespie D. D. #342-237-82929Jack, TX · Lode Holdings LLC1.34RESISTIVITYTIFF0 to 474Mar 7, 2016run Aug 25, 2011
Gillespie D. D. #9C42-237-39417Jack, TX · Lode Holdings LLC1.37Gamma RayTIFF0 to 550Oct 29, 2018
Richards Frank #742-237-39963Jack, TX · Paratus Petroleum LLC1.37Induction2 TIFF505 to 5,870Oct 18, 2018
Gillespie D. D. #11C42-237-39420Jack, TX · Lode Holdings LLC1.43NEUTRON POROSITYTIFF199 to 572May 20, 2015run May 18, 2011
Gillespie D. D. #1C42-237-39410Jack, TX · Lode Holdings LLC1.47NEUTRON POROSITYTIFF139 to 538May 20, 2015run May 18, 2011
Ruth Peek a #342-237-38025Jack, TX · Jonco1.62ResistivityTIFFPHASER INDUCTION SPHERICALLY FOCUSED LOG490 to 5,100Mar 6, 2008run May 18, 1993
Moore #5142-237-39398Jack, TX · Erwin Oil Company1.85RESISTIVITYTIFF0 to 498Jul 28, 2015run Apr 25, 2011

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.