WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-435-30989
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 7 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Johnson JO Nell 18 #742-435-39294Sutton, TX · Upp Operating LLC | 0.91 | NEUTRON/DENSITY POROSITYTIFF | 6,700 to 9,233 | Aug 6, 2012run Jun 28, 2010 |
| Johnson JO Nell 18 #742-435-39294Sutton, TX · Upp Operating LLC | 0.91 | RESISTIVITYTIFF | 200 to 9,270 | Aug 6, 2012run Jun 28, 2010 |
| Mrs May M Ray #542-435-39213Sutton, TX · Upp Operating LLC | 1.75 | NEUTRON/DENSITY POROSITYTIFF | 200 to 9,454 | Oct 22, 2012run Oct 29, 2009 |
| Mrs May M Ray #542-435-39213Sutton, TX · Upp Operating LLC | 1.75 | RESISTIVITYTIFF | 6,400 to 9,454 | Oct 22, 2012run Oct 29, 2009 |
| Ray Ranch B #114242-435-37207Sutton, TX · Upp Operating LLC | 1.78 | NEUTRON/DENSITY POROSITYTIFF | 4,500 to 9,368 | Feb 12, 2009run Jan 17, 2006 |
| Ray Ranch B #114242-435-37207Sutton, TX · Upp Operating LLC | 1.78 | RESISTIVITYTIFF | 4,500 to 9,368 | Feb 12, 2009run Jan 17, 2006 |
| Cauthorn -F- #542-465-30756Val Verde, TX · White Rock Oil & Gas LLC | 1.83 | NEUTRON/DENSITY POROSITYTIFF | 995 to 9,314 | Jun 4, 2009run May 5, 2006 |
| Cauthorn -F- #542-465-30756Val Verde, TX · White Rock Oil & Gas LLC | 1.83 | RESISTIVITYTIFF | 995 to 10,202 | Jun 4, 2009run May 13, 2006 |
| J. A. Ranch -K- #142-465-30730Val Verde, TX · Conocophillips Company | 1.95 | Acoustic PorosityTIFFDIPOLE SHEAR SONIC IMAGER GAMMA RAY | 8,000 to 10,343 | Apr 17, 2008run Jun 8, 2004 |
| J. A. Ranch -K- #142-465-30730Val Verde, TX · Conocophillips Company | 1.95 | Neutron/Density PorosityTIFFCOMPENSATED NEUTRON THREE DETECTOR LITHODENSITY | 8,000 to 10,343 | Apr 17, 2008run Jun 8, 2004 |
| J. A. Ranch -K- #142-465-30730Val Verde, TX · Conocophillips Company | 1.95 | Resistivity2 TIFFHIGH RESOLUTION LATEROLOG ARRAY GAMMA RAY | 8,000 to 10,343 | Apr 17, 2008run Jun 8, 2004 |
| Ranch. J. A. -L- #442-465-30790Val Verde, TX · White Rock Oil & Gas LLC | 1.97 | NEUTRON/DENSITY POROSITYTIFF | 1,024 to 10,371 | Jul 23, 2009run Jul 20, 2006 |
| Ranch. J. A. -L- #442-465-30790Val Verde, TX · White Rock Oil & Gas LLC | 1.97 | RESISTIVITYTIFF | 1,024 to 10,349 | Jul 23, 2009run Jul 20, 2006 |
| Ranch J. A. -K- #342-465-30789Val Verde, TX · White Rock Oil & Gas LLC | 1.98 | NEUTRON/DENSITY POROSITYTIFF | 2,500 to 9,302 | Aug 6, 2009run Jun 5, 2006 |
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.