WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-383-00971
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.
16 LOG FILES ON 15 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Chico Company #228A42-383-37429Reagan, TX · RP Operating L.L.C. | 0.72 | NEUTRON/DENSITY POROSITYTIFF | 200 to 9,223 | Oct 29, 2014run Oct 23, 2011 |
| Chico Company #228I42-383-37428Reagan, TX · RP Operating L.L.C. | 0.78 | NEUTRON/DENSITY POROSITYTIFF | 200 to 9,242 | Oct 30, 2014run Oct 6, 2011 |
| Chico Company #242-383-36916Reagan, TX · RP Operating L.L.C. | 1.16 | NEUTRON/DENSITY POROSITYTIFF | 200 to 8,236 | Sep 16, 2013run Sep 14, 2010 |
| Big Lake 225 SWD #142-383-38013Reagan, TX · Select Energy Services LLC | 1.37 | NEUTRON POROSITYTIFF | 50 to 3,498 | Feb 3, 2014run Oct 18, 2013 |
| Chico East 2-28 Alloc 02 #206HSHZ42-383-40164Reagan, TX · Permian Resources Operating LLC | 1.39 | Gamma RayLAS + TIFF | 1,238 to 17,694 | Feb 2, 2022 |
| Black Mountain 227 SWD #142-383-38119Reagan, TX · Ogris Operating LLC | 1.40 | RESISTIVITYTIFF | 2,836 to 3,696 | May 9, 2013run Dec 11, 2012 |
| Chico Company #228E42-383-38502Reagan, TX · RP Operating L.L.C. | 1.41 | NEUTRON/DENSITY POROSITYTIFF | 200 to 9,393 | Dec 30, 2016run Dec 27, 2013 |
| Ponderosa #142-383-37486Reagan, TX · Byrd Oilfield Services LLC | 1.46 | RESISTIVITYTIFF | 1,100 to 2,594 | Feb 12, 2018run Sep 21, 2011 |
| Chico Company #4P42-383-38099Reagan, TX · RP Operating L.L.C. | 1.64 | RESISTIVITYTIFF | 4,500 to 9,341 | Sep 13, 2016run Sep 13, 2013 |
| Peach B 231-224 #1HHZ42-383-40701Reagan, TX · RP Operating L.L.C. | 1.65 | Gamma RayTIFF | 0 to 17,461 | Oct 8, 2024 |
| Chico East Allocation a #236HSHZ42-383-40026Reagan, TX · Permian Resources Operating LLC | 1.81 | Gamma RayTIFF | 967 to 17,661 | Oct 22, 2020 |
| University Tema #1HHZ42-383-40068Reagan, TX · R2Q Operating LLC | 1.83 | Cement BondTIFF | 6,000 to 12,250 | Apr 6, 2021 |
| Chico Company #4G42-383-38525Reagan, TX · RP Operating L.L.C. | 1.88 | RESISTIVITYTIFF | 4,100 to 9,323 | Jan 30, 2017run Jan 22, 2014 |
| Chico Company #4A42-383-37434Reagan, TX · RP Operating L.L.C. | 1.89 | COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF | 934 to 9,425 | Nov 12, 2014run Nov 4, 2011 |
| Husky #2142-383-35471Reagan, TX · Atlas Operating LLC | 1.90 | ResistivityTIFFHIGH RESOLUTION LATEROLOG ARRAY GAMMA RAY | 1,693 to 2,693 | Apr 7, 2008run Nov 20, 2004 |
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.