WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-003-35751

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-003-35751Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Dollarhide Unit #3410CT42-003-45149Andrews, TX · Scout Energy Management LLC0.48NEUTRON POROSITYTIFF0 to 7,513Jul 21, 2014run Jul 5, 2013
Dollarhide Unit #3517CT42-003-45130Andrews, TX · Scout Energy Management LLC0.52NEUTRON POROSITYTIFF0 to 7,502May 6, 2014run Apr 18, 2013
Dollarhide Unit #3517CT42-003-45130Andrews, TX · Scout Energy Management LLC0.52NEUTRON POROSITYTIFF0 to 7,502May 26, 2014run Apr 18, 2013
Dollarhide Unit #3515S42-003-39711Andrews, TX · Scout Energy Management LLC0.55Neutron/Density PorosityTIFFSPECTRAL DENSITY DUAL SPACED NEUTRON SPECTRAL GAMMA RAY200 to 9,053Oct 19, 2007run Mar 19, 2006
Dollarhide Unit #394S42-003-39710Andrews, TX · Scout Energy Management LLC0.58Neutron/Density PorosityTIFFSPECTRAL DENSITY DUAL SPACED NEUTRON SPECTRAL GAMMA LOG200 to 8,850Sep 18, 2007run Jan 31, 2006
Dollarhide Unit #3310CT42-003-45131Andrews, TX · Scout Energy Management LLC0.60COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF3,209 to 7,165Jul 3, 2017run Jul 20, 2013
Dollarhide Unit #3310CT42-003-45131Andrews, TX · Scout Energy Management LLC0.60NEUTRON POROSITYTIFF0 to 7,515Nov 12, 2014run Jul 25, 2013
Dollarhide Unit #3310CT42-003-45131Andrews, TX · Scout Energy Management LLC0.60RESISTIVITY4 TIFF3,209 to 7,165Jul 3, 2017run Jul 20, 2013
Dollarhide Unit #255S42-003-39712Andrews, TX · Scout Energy Management LLC0.65Neutron/Density PorosityTIFFSPECTRAL DENSITY DUAL SPACED NEUTRON SPECTRAL GAMMA RAY200 to 8,956Nov 13, 2007run Apr 16, 2006
Dollarhide Unit #2507S42-003-42693Andrews, TX · Scout Energy Management LLC0.77NEUTRON/DENSITY POROSITYTIFF200 to 8,946Oct 2, 2013run Apr 28, 2011
Dollarhide Unit #256S42-003-39713Andrews, TX · Scout Energy Management LLC1.01Neutron/Density PorosityTIFFSPECTRAL DENSITY DUAL-SPACED NEUTRON SPECTRAL GAMMA200 to 9,043Sep 18, 2007run Feb 22, 2006
Dollarhide Unit #2305CT42-003-43976Andrews, TX · Scout Energy Management LLC1.17ACOUSTIC POROSITYTIFF3,238 to 7,529Oct 8, 2013run Aug 25, 2012
Dollarhide Unit #2305CT42-003-43976Andrews, TX · Scout Energy Management LLC1.17NEUTRON/DENSITY POROSITY2 TIFF3,238 to 7,529Oct 1, 2013run Aug 25, 2012
Dollarhide Unit #2305CT42-003-43976Andrews, TX · Scout Energy Management LLC1.17RESISTIVITYTIFF3,238 to 7,529Oct 1, 2013run Aug 25, 2012
Dollarhide Unit #2305CT42-003-43976Andrews, TX · Scout Energy Management LLC1.17RESISTIVITYTIFF3,238 to 7,529Oct 8, 2013run Aug 25, 2012
Dollarhide Unit #1305DHZ42-003-32277Andrews, TX · Scout Energy Management LLC1.38NEUTRON POROSITYTIFF6,000 to 7,985May 8, 2013run Mar 18, 2010
Dollarhide Unit #1305DHZ42-003-32277Andrews, TX · Scout Energy Management LLC1.38RESISTIVITYTIFF4,980 to 8,053May 8, 2013run Mar 18, 2010
Dollarhide Unit #2045CT42-003-43977Andrews, TX · Scout Energy Management LLC1.39NEUTRON/DENSITY POROSITYTIFF200 to 7,476Sep 30, 2013run Aug 14, 2012
Dollarhide Unit #2045CT42-003-43977Andrews, TX · Scout Energy Management LLC1.39NEUTRON/DENSITY POROSITYTIFF3,243 to 7,592Sep 30, 2013run Aug 8, 2012
Dollarhide Unit #1922CT42-003-43978Andrews, TX · Scout Energy Management LLC1.60NEUTRON/DENSITY POROSITYTIFF3,242 to 7,610Aug 27, 2013run Jul 20, 2012
Dollarhide Unit #1922CT42-003-43978Andrews, TX · Scout Energy Management LLC1.60RESISTIVITY5 TIFF3,242 to 7,610Aug 27, 2013run Jul 20, 2012
Dollarhide Unit #1922CT42-003-43978Andrews, TX · Scout Energy Management LLC1.60RESISTIVITYTIFF3,242 to 7,610Feb 3, 2014run Jul 20, 2012
Dollarhide Unit #1922CT42-003-43978Andrews, TX · Scout Energy Management LLC1.60RESISTIVITYTIFF5,239 to 10,398Aug 27, 2013run Jul 20, 2012
Dollarhide Unit #203CT42-003-43979Andrews, TX · Scout Energy Management LLC1.84NEUTRON POROSITY2 TIFF200 to 7,511Sep 30, 2013run Jul 5, 2012
Dollarhide Unit #203CT42-003-43979Andrews, TX · Scout Energy Management LLC1.84RESISTIVITYTIFF200 to 7,511Nov 18, 2013run Jul 5, 2012
Dollarhide Unit #0768CT42-003-45240Andrews, TX · Scout Energy Management LLC1.97NEUTRON POROSITYTIFF0 to 7,521May 28, 2014run May 21, 2013
Dollarhide Unit #0768CT42-003-45240Andrews, TX · Scout Energy Management LLC1.97NEUTRON POROSITYTIFF0 to 7,521May 27, 2014run May 21, 2013
Dollarhide Unit #0768CT42-003-45240Andrews, TX · Scout Energy Management LLC1.97RESISTIVITYTIFF0 to 7,521May 28, 2014run May 21, 2013

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.