WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-321-80134
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.
13 LOG FILES ON 11 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Harriman #0142-321-31974Matagorda, TX · Progenies Operating LLC | 0.56 | Acoustic PorosityTIFFARRAY INDUCTION, BOREHOLE COMPENSATED SONIC, | 1,214 to 9,510 | Oct 31, 2006run Aug 31, 2003 |
| Big Mac Blessing #142-321-32355Matagorda, TX · Kebo Oil & Gas Inc. | 0.75 | InductionTIFF | 2,517 to 10,965 | Dec 11, 2018 |
| Big Mac Blessing #142-321-32355Matagorda, TX · Kebo Oil & Gas Inc. | 0.75 | RESISTIVITYTIFF | 2,519 to 10,965 | May 10, 2016run Apr 8, 2013 |
| Pheasant Blessing #142-321-32289Matagorda, TX · Dallas Petroleum Group LLC | 0.96 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 2,496 to 10,998 | Dec 21, 2012run Nov 14, 2009 |
| Pheasant Blessing #142-321-32289Matagorda, TX · Dallas Petroleum Group LLC | 0.96 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 7,008 to 10,998 | Oct 1, 2013run Nov 14, 2009 |
| Beulah #242-321-32105Matagorda, TX · Sue-Ann Operating L.C. | 1.16 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 1,188 to 9,315 | Jul 22, 2009run Jul 16, 2006 |
| Trull SWP #242-321-32447Matagorda, TX · Kebo Oil & Gas Inc. | 1.54 | InductionTIFF | 1,251 to 8,500 | Nov 21, 2025 |
| South Blessing #242-321-32336Matagorda, TX · Kebo Oil & Gas Inc. | 1.54 | RESISTIVITYTIFF | 2,520 to 11,500 | May 23, 2013run Apr 25, 2012 |
| Northwest Blessing #142-321-32207Matagorda, TX · Kebo Oil & Gas Inc. | 1.67 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 2,511 to 12,344 | May 15, 2009run Apr 11, 2008 |
| West Blessing Gas Unit B #142-321-32244Matagorda, TX · Dallas Petroleum Group LLC | 1.84 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 2,500 to 9,905 | Nov 28, 2011run Oct 25, 2008 |
| Yeamans Blessing #142-321-32313Matagorda, TX · Kebo Oil & Gas Inc. | 1.90 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 2,516 to 11,541 | Oct 21, 2013run Oct 17, 2010 |
| Wilson Trust #142-321-32001Matagorda, TX · Hemco Development LLC | 1.94 | Combination: Resistivity/Neutron Density PorosityTIFFARRAY INDUCTION COMP. NEUTRON LITHO-DENSITY | 1,999 to 9,628 | Sep 21, 2007run Apr 22, 2004 |
| South Blessing #142-321-32190Matagorda, TX · Kebo Oil & Gas Inc. | 1.99 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 2,522 to 11,786 | Oct 28, 2008run Oct 5, 2007 |
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.