WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-389-35656

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-389-35656Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Sansom 3875 Alloc C #23HHZ42-389-38221Reeves, TX · Apache Corporation0.12Gamma RayLAS + TIFF2,250 to 22,150Jul 31, 2022
Sansom 3875 Alloc B #21HHZ42-389-38220Reeves, TX · Apache Corporation0.13Gamma RayLAS + TIFF2,150 to 21,798Jul 31, 2022
Central Reeves #2SW42-389-34341Reeves, TX · Waterbridge Texas Operating LLC0.21ResistivityTIFF2,194 to 6,736Mar 20, 2019
Samurai 4-49 50 #u 35HHZ42-389-36277Reeves, TX · Permian Resources Operating LLC0.28Gamma RayTIFF797 to 10,476Dec 8, 2020
Samurai 4-49 50 #u 35HHZ42-389-36277Reeves, TX · Permian Resources Operating LLC0.28Measure While Drilling (MWD)TIFF5,500 to 20,175Feb 27, 2019
Richmond 39 #3HHZ42-389-36169Reeves, TX · Apache Corporation0.49Gamma RayTIFF2,150 to 21,750Apr 28, 2021
Richmond 39 #2HHZ42-389-36010Reeves, TX · Apache Corporation0.50Gamma RayTIFF2,200 to 21,000Apr 28, 2021
Ninja 4-50 49 #5HHZ42-389-36095Reeves, TX · Permian Resources Operating LLC0.62Gamma RayLAS + TIFF4,200 to 20,180Apr 30, 2021
Ninja 4-50 49 #5HHZ42-389-36095Reeves, TX · Permian Resources Operating LLC0.62Measure While Drilling (MWD)TIFF4,200 to 20,180Feb 27, 2019
Dorothy Unit 38 #1HZ42-389-36137Reeves, TX · Apache Corporation0.65Gamma RayLAS + TIFF10,575 to 19,955Sep 25, 2020
Fox 37 A3 #10UAHZ42-389-39712Reeves, TX · Apache Corporation0.69Gamma RayLAS + TIFF0 to 10,036Jul 23, 2025
Ninja 4-50 49 #4HHZ42-389-36088Reeves, TX · Permian Resources Operating LLC0.69Gamma RayLAS + TIFF4,200 to 20,654May 4, 2021
Ninja 4-50 49 #4HHZ42-389-36088Reeves, TX · Permian Resources Operating LLC0.69Measure While Drilling (MWD)TIFF4,210 to 20,654Feb 27, 2019
Fox 37 A4 #3LAHZ42-389-39713Reeves, TX · Apache Corporation0.69Gamma RayLAS + TIFF0 to 10,030Jul 23, 2025
Fox 37 A1 #5HHZ42-389-39710Reeves, TX · Apache Corporation0.70Gamma RayLAS + TIFF10,778 to 20,704Apr 30, 2025
Smith-State 4-42 #1HHZ42-389-33564Reeves, TX · Apache Corporation0.84COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF200 to 10,604Jun 16, 2016run Apr 8, 2013
Smith-State 4-42 #1HHZ42-389-33564Reeves, TX · Apache Corporation0.84COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF10,580 to 12,228Jun 16, 2016run Apr 23, 2013
Smith-State 4-42 #1HHZ42-389-33564Reeves, TX · Apache Corporation0.84RESISTIVITYTIFF4,501 to 10,604May 17, 2016run Apr 8, 2013
Smith-State 4-42 #1HHZ42-389-33564Reeves, TX · Apache Corporation0.84RESISTIVITYTIFF4,501 to 10,604Apr 11, 2018run Apr 8, 2013
Smith-State 4-42 #1HHZ42-389-33564Reeves, TX · Apache Corporation0.84RESISTIVITYTIFF10,580 to 12,228Aug 25, 2016run Apr 23, 2013
Zeman-State Alloc a 4042 #10HHZ42-389-36303Reeves, TX · Apache Corporation0.86Cement BondTIFF9,000 to 10,740Nov 2, 2017
Zeman 40 Alloc. C #11HHZ42-389-36767Reeves, TX · Apache Corporation0.86Gamma RayLAS + TIFF2,250 to 18,572Mar 30, 2021
Ninja 4-50 49 #2HHZ42-389-36652Reeves, TX · Permian Resources Operating LLC0.87Gamma RayLAS + TIFF825 to 20,956May 4, 2021
Ninja 4-50 49 #2HHZ42-389-36652Reeves, TX · Permian Resources Operating LLC0.87Measure While Drilling (MWD)TIFF825 to 20,956Feb 27, 2019
Ninja 4-50 49 #3HHZ42-389-36653Reeves, TX · Permian Resources Operating LLC0.88Gamma RayLAS + TIFF714 to 20,760Mar 12, 2021
Ninja 4-50 49 #3HHZ42-389-36653Reeves, TX · Permian Resources Operating LLC0.88Measure While Drilling (MWD)TIFF810 to 18,939Feb 27, 2019
Richmond W State 4239 a-D #73HHZ42-389-38704Reeves, TX · Apache Corporation0.92Gamma RayLAS + TIFF2,350 to 18,855Feb 28, 2023
Richmond W State 4239 a-C #72HHZ42-389-38703Reeves, TX · Apache Corporation0.92Measure While Drilling (MWD)LAS + TIFF2,350 to 18,751Jan 27, 2025
Richmond W State 4239 a-B #71HHZ42-389-38702Reeves, TX · Apache Corporation0.92Measure While Drilling (MWD)LAS + TIFF2,350 to 14,605Jan 27, 2025
Zeman-State A8 #2LAHZ42-389-40396Reeves, TX · Apache Corporation0.92Measure While Drilling (MWD)LAS + TIFF2,338 to 18,467Jan 21, 2026
Richmond W State 4239 a-a #70HHZ42-389-38701Reeves, TX · Apache Corporation0.93Gamma RayLAS + TIFF2,350 to 18,210Dec 15, 2022
Zeman-State A9 #6HHZ42-389-40397Reeves, TX · Apache Corporation0.93Measure While Drilling (MWD)LAS + TIFF2,338 to 19,029Feb 25, 2026
Richmond W. State 4239 A5 #6HHZ42-389-40212Reeves, TX · Apache Corporation1.00Measure While Drilling (MWD)LAS2,252 to 18,681Dec 10, 2025

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.