WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-131-10808

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-131-10808Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
White P. E. -B- #14742-131-39482Duval, TX · Killam Oil Co. Ltd.0.32NEUTRON/DENSITY POROSITYTIFF514 to 2,663Aug 14, 2017run Aug 6, 2014
White P. E. -B- #15542-131-39646Duval, TX · Killam Oil Co. Ltd.0.41InductionTIFF515 to 2,707Aug 18, 2023
DCR-State 260 F #1642-131-38989Duval, TX · Killam Oil Co. Ltd.0.58COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF108 to 1,822Jul 26, 2010run Jul 11, 2007
Lundell State 140 #142-131-38615Duval, TX · Hilcorp Energy Company0.62Combination: Resistivity/Neutron Density PorosityTIFFARRAY INDUCTION GR LITHO DENSITY COMP. NEUTRON PATFORM EXPRESS 1507,131 to 8,212Dec 3, 2007run Jun 15, 2003
Killam 257 #2142-131-39300Duval, TX · Killam Oil Co. Ltd.0.65COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF524 to 4,014Nov 10, 2015run Nov 19, 2012
Lundell-State 140 #442-131-38988Duval, TX · Killam Oil Co. Ltd.0.75COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF103 to 1,778Jul 26, 2010run Jul 17, 2007
White P. E. -B- #15242-131-39626Duval, TX · Killam Oil Co. Ltd.0.76InductionTIFF470 to 1,772Oct 4, 2024
DCR-State 260 F #1742-131-39034Duval, TX · Killam Oil Co. Ltd.0.76COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF104 to 1,810Dec 14, 2010run Nov 27, 2007
DCR-State 260 F #1542-131-38949Duval, TX · Killam Oil Co. Ltd.0.77COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF185 to 1,799Jan 29, 2010run Jan 30, 2007
Lundell-State 140 #542-131-39028Duval, TX · Killam Oil Co. Ltd.0.79COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF102 to 1,825Dec 14, 2010run Nov 14, 2007
Lundell-State 140 #642-131-39625Duval, TX · Killam Oil Co. Ltd.0.83InductionTIFF450 to 1,828Oct 4, 2024
Killam 257 #2042-131-38082Duval, TX · Killam Oil Co. Ltd.0.84COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF50 to 1,765Nov 4, 2008run Mar 12, 1996
White P. E. -B- #14842-131-39523Duval, TX · Killam Oil Co. Ltd.1.09NEUTRON/DENSITY POROSITYTIFF500 to 2,652Dec 13, 2017run Nov 3, 2014
White P. E. -B- #14942-131-39525Duval, TX · Killam Oil Co. Ltd.1.35NEUTRON/DENSITY POROSITYTIFF514 to 2,672Dec 8, 2017run Dec 3, 2014
Duval County Ranch Co. State V #1642-131-39624Duval, TX · Killam Oil Co. Ltd.1.92InductionTIFF555 to 2,748Oct 4, 2024

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.