WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-409-30561

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-409-30561Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Schuster #142-409-32806San Patricio, TX · Slawson Exploration Company Inc0.35COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF494 to 2,799Oct 29, 2008run Oct 1, 2005
Schuster #242-409-32841San Patricio, TX · Slawson Exploration Company Inc0.50COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF470 to 2,980Sep 3, 2009run Aug 23, 2006
Floerke #242-409-32842San Patricio, TX · Slawson Exploration Company Inc0.64COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF416 to 3,068Sep 17, 2009run Sep 22, 2006
McBride #142-409-32808San Patricio, TX · Slawson Exploration Company Inc0.67COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF534 to 2,218Oct 29, 2008run Oct 9, 2005
Asbury #242-409-32828San Patricio, TX · Slawson Exploration Company Inc0.96COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF460 to 4,154May 8, 2009run Apr 11, 2006
Blackman #1__42-409-32454San Patricio, TX · Suemaur Exploration Inc.1.15COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,037 to 8,471Aug 22, 2008run Sep 28, 1994
Blackman-Hutto #142-409-32781San Patricio, TX · Slawson Exploration Company Inc1.36COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF410 to 2,750Sep 11, 2008run Apr 14, 2005
Lucky Jones #142-409-32837San Patricio, TX · EOG Resources Inc.1.42RESISTIVITYTIFF0 to 11,787Oct 1, 2009run Sep 22, 2006
Bell Farms #142-409-32740San Patricio, TX · Proline Energy Resources Inc1.60ResistivityTIFFHIGH DEFINITION INDUCTION GAMMA RAY2,508 to 10,992Nov 14, 2006run Oct 14, 2003
Bell Farms #342-409-32812San Patricio, TX · Proline Energy Resources Inc1.61RESISTIVITYTIFF11,045 to 12,376Feb 13, 2009run Jan 1, 2006
Bell Farms #242-409-32760San Patricio, TX · Proline Energy Resources Inc1.61ResistivityTIFFHIGH DEFINITION INDUCTION GAMMA RAY LOG11,059 to 14,778Feb 27, 2008run Aug 21, 2004
Jones Estate #242-409-32800San Patricio, TX · Proline Energy Resources Inc1.62RESISTIVITYTIFF2,528 to 10,986Nov 19, 2008run Aug 14, 2005
Jones Estate #342-409-32859San Patricio, TX · Proline Energy Resources Inc1.78RESISTIVITYTIFF2,506 to 11,762Mar 31, 2010run Mar 17, 2007
Smith L #442-409-32807San Patricio, TX · Proline Energy Resources Inc1.85RESISTIVITYTIFF2,500 to 13,872Nov 19, 2008run Oct 30, 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.