WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of Rhino 37 #1 (42-389-33352)

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 Rhino 37 #1 (42-389-33352)Clear

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.

26 LOG FILES ON 12 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Rhino 37 #142-389-33352Reeves, TX · Crescent Energy Operating LLChereCOMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF5,108 to 11,636Apr 14, 2016run Apr 14, 2013
Rhino 37 #142-389-33352Reeves, TX · Crescent Energy Operating LLChereRESISTIVITYTIFF200 to 11,594Apr 11, 2016run Jun 26, 2013
Coyote 48 #242-371-39090Pecos, TX · Crescent Energy Operating LLC0.45NEUTRON POROSITYTIFF3,200 to 11,419Aug 11, 2016run Mar 13, 2014
Coyote 48 #142-371-38939Pecos, TX · Crescent Energy Operating LLC0.87NEUTRON POROSITYTIFF0 to 11,694Feb 29, 2016run Mar 5, 2013
Coyote 48 #142-371-38939Pecos, TX · Crescent Energy Operating LLC0.87RESISTIVITYTIFF7,100 to 11,770Feb 22, 2016run Mar 5, 2013
McCombs State 1-12 #3BSHZ42-371-40040Pecos, TX · Diamondback E&P LLC1.21Cement BondTIFF0 to 9,350Sep 21, 2022
Iron Mike 40SE #2HHZ42-389-34807Reeves, TX · Crescent Energy Operating LLC1.25Gamma RayTIFF200 to 11,504Sep 13, 2018
McCombs State 1-12 #5WAHZ42-371-40111Pecos, TX · Diamondback E&P LLC1.26Cement BondTIFF0 to 10,521Dec 31, 2022
Balbo West-Elliot #1HHZ42-371-39508Pecos, TX · Halcon Operating Co. Inc.1.71Gamma RayTIFF2,471 to 20,565Oct 27, 2020
Lynx 38N #1HHZ42-389-33916Reeves, TX · Crescent Energy Operating LLC1.73COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF9,436 to 11,017Feb 3, 2017run Oct 30, 2013
Lynx 38N #1HHZ42-389-33916Reeves, TX · Crescent Energy Operating LLC1.73RESISTIVITYTIFF3,000 to 11,006Feb 3, 2017run Nov 1, 2013
Lynx 38N #1HHZ42-389-33916Reeves, TX · Crescent Energy Operating LLC1.73RESISTIVITY5 TIFF9,436 to 11,017Feb 3, 2017run Oct 30, 2013
Lynx 38N #1HHZ42-389-33916Reeves, TX · Crescent Energy Operating LLC1.73RESISTIVITYTIFF9,800 to 17,762Feb 3, 2017run Jan 3, 2014
Lynx 38N #1HHZ42-389-33916Reeves, TX · Crescent Energy Operating LLC1.73RESISTIVITY3 TIFF11,078 to 17,702Feb 3, 2017run Dec 30, 2013
Liger 22-34-5N #24HHZ42-389-36959Reeves, TX · Crescent Energy Operating LLC1.80Measure While Drilling (MWD)LAS + TIFF4,950 to 23,005Feb 21, 2022
Bengal 27-34-4N #23HHZ42-389-36958Reeves, TX · Crescent Energy Operating LLC1.81Measure While Drilling (MWD)LAS + TIFF10,190 to 20,524Feb 21, 2022
Lindsay #1D42-371-39771Pecos, TX · Rattler Midstream Operating LLC1.88Cement BondTIFF0 to 8,147Feb 22, 2023
Red Horse 31 #142-389-32544Reeves, TX · Shenandoah Petroleum Corporation1.91NEUTRON/DENSITY POROSITYTIFF190 to 5,504Nov 15, 2011run Oct 2, 2008

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.