WELL LOGS · UNITED STATES · ONE ROW PER LOG
Ector County well logs
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.
5,165 LOG FILES ON 4,208 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 104 OF 104
| Well | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|
| Meteor Crater #142-135-38345Ector, TX · OXY USA WTP LP | Neutron/Density PorosityTIFFSPECTRAL DENSITY DUAL SPACED NEUTRON SPECTRAL GAMMA | 200 to 11,864 | Jul 18, 2006run Apr 8, 2003 |
| East Cowden (Grayburg) Unit #9342-135-38321Ector, TX · GL Energy Operating LLC | Neutron/Density PorosityTIFFPLATFORM EXPRESS COMPENSATED NEUTRON THREE DETECTOR LITHODENSITY | 200 to 4,680 | Jul 14, 2006run Jun 19, 2003 |
| East Cowden (Grayburg) Unit #9142-135-38318Ector, TX · GL Energy Operating LLC | Neutron/Density PorosityTIFFPLATFORM EXPRESS COMPENSATED NEUTRON THREE DETECTOR LITHODENSITY | 200 to 4,648 | Jul 14, 2006run Jun 18, 2003 |
| East Cowden (Grayburg) Unit #9242-135-38319Ector, TX · GL Energy Operating LLC | ResistivityTIFFPLATFORM EXPRESS HIGH RESOLUTION LATEROLOG ARRAY | 1,605 to 4,676 | Jul 14, 2006run Jun 9, 2003 |
| Goldsmith Adobe Unit #391542-135-37369Ector, TX · Crescent Energy Operating LLC | Neutron/Density PorosityTIFFCOMPENSATED NEUTRON LITHODENSITY | 3,700 to 5,901 | Jul 14, 2006run Jan 6, 1997 |
| Goldsmith Adobe Unit #290942-135-38395Ector, TX · Crescent Energy Operating LLC | Neutron/Density PorosityTIFFPLATFORM EXPRESS THREE DETECTOR LITHO DENSITY COMPENSATED NEUTRON-GR | 200 to 6,110 | Jul 11, 2006run May 12, 2003 |
| Goldsmith Adobe Unit #350242-135-38396Ector, TX · Crescent Energy Operating LLC | Neutron/Density PorosityTIFFPLATFORM EXPRESS THREE DETECTOR LITHO DENSITY COMPENSATED NEUTRON/GAMMA RAY | 300 to 6,090 | Jul 11, 2006run Apr 30, 2003 |
| TXL North Unit #92642-135-38641Ector, TX · Anadarko Petroleum Corporation | Neutron PorosityTIFFGAMMA RAY/CCL COMPENSATED NEUTRON | 5,000 to 6,609 | Jul 6, 2006run Jul 6, 2004 |
| South Foster Unit #20942-135-38165Ector, TX · Occidental Permian Ltd. | NEUTRON/DENSITY POROSITYTIFF | 3,000 to 4,185 | Jul 29, 2002run Oct 17, 2001 |
| Gist Unit #17142-135-37911Ector, TX · Aghorn Operating Inc. | NEUTRON POROSITYTIFF | 3,700 to 4,547 | May 17, 2002run Apr 11, 2001 |
| Gist Unit #16742-135-37915Ector, TX · Aghorn Operating Inc. | NEUTRON POROSITYTIFF | 3,700 to 4,508 | May 17, 2002run Mar 16, 2001 |
| Gist Unit #16642-135-37914Ector, TX · Aghorn Operating Inc. | NEUTRON POROSITYTIFF | 3,700 to 4,503 | May 17, 2002run Mar 6, 2001 |
| Madison #142-135-37732Ector, TX · Anadarko E&P Company LP | ACOUSTIC POROSITYTIFF | 300 to 12,570 | May 17, 2002run Oct 14, 1998 |
| Madison #142-135-37732Ector, TX · Anadarko E&P Company LP | NEUTRON/DENSITY POROSITYTIFF | 0 to 12,570 | May 17, 2002run Oct 4, 1998 |
| Goldsmith Andector Unit #f 6542-135-38012Ector, TX · Maverick Permian LLC | NEUTRON/DENSITY POROSITYTIFF | to 6,500 | May 8, 2002run Mar 20, 2001 |
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.