WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-363-20102

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-363-20102Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Halsell Ranch Richey #b 2242-363-36304Palo Pinto, TX · Eagleridge Operating LLC0.16RESISTIVITYTIFF3,320 to 5,044Aug 7, 2016run Sep 10, 2015
Boedeker #b 142-363-36286Palo Pinto, TX · Eagleridge Operating LLC0.53RESISTIVITYTIFF2,890 to 5,134Aug 7, 2016run Sep 10, 2015
Gauldin NE #142-363-36298Palo Pinto, TX · FX Energy Operating LLC0.90ResistivityTIFF500 to 5,300Oct 23, 2018
Halsell Ranch #b 1642-363-36264Palo Pinto, TX · Eagleridge Operating LLC1.01Cement BondTIFF100 to 5,050Oct 9, 2018
Lane Green #242-363-36160Palo Pinto, TX · FX Energy Operating LLC1.03NEUTRON/DENSITY POROSITYTIFF498 to 5,136Aug 31, 2016run Aug 22, 2013
Halsell Dallas Production Unit #b 1742-363-36269Palo Pinto, TX · Eagleridge Operating LLC1.22InductionTIFF300 to 5,152Aug 31, 2018
Halsell Dallas Production Unit #b 1742-363-36269Palo Pinto, TX · Eagleridge Operating LLC1.22RESISTIVITYTIFF3,400 to 5,094May 26, 2015run Dec 23, 2014
Otis Sikes SWD #142-363-36307Palo Pinto, TX · Brigadier Operating LLC1.37RESISTIVITYTIFF0 to 231Dec 5, 2016run Aug 3, 2015
Halsell Dallas Production Unit #b 1542-363-36268Palo Pinto, TX · Eagleridge Operating LLC1.41InductionTIFF500 to 5,336Aug 31, 2018
Halsell Dallas Production Unit #b 1542-363-36268Palo Pinto, TX · Eagleridge Operating LLC1.41RESISTIVITYTIFF3,800 to 5,284May 26, 2015run Jan 5, 2015
Halsell Ranch #s 642-363-36073Palo Pinto, TX · Texxol Operating Company Inc.1.42RESISTIVITYTIFF228 to 4,772May 20, 2015run May 28, 2012
Halsell Ranch #b 1842-237-40349Jack, TX · Eagleridge Operating LLC1.58InductionTIFF300 to 5,173Aug 31, 2018
Seale #142-363-36176Palo Pinto, TX · FX Energy Operating LLC1.65NEUTRON/DENSITY POROSITYTIFF498 to 5,295Jan 30, 2017run Nov 12, 2013
Hasel #242-237-38898Jack, TX · Cholla Petroleum Inc.1.71ResistivityTIFFDUAL INDUCTION FOCUESD LOG200 to 2,008Aug 24, 2007run Nov 22, 2005
Hasel #242-237-38898Jack, TX · Cholla Petroleum Inc.1.71RESISTIVITYTIFF175 to 4,527Sep 9, 2008run Oct 19, 2006
Halsell Ranch Cholla #b 2142-237-40358Jack, TX · Eagleridge Operating LLC1.74InductionTIFF300 to 5,104Aug 31, 2018
Halsel #3__42-237-38897Jack, TX · Cholla Petroleum Inc.1.94RESISTIVITYTIFF187 to 4,558Jan 28, 2010run Nov 2, 2006
Halsell J. R. #642-363-36035Palo Pinto, TX · Keating Energy Inc.1.98RESISTIVITYTIFF224 to 5,085Apr 17, 2012run Aug 14, 2011
Halsell J. R. #642-363-36035Palo Pinto, TX · Keating Energy Inc.1.98RESISTIVITYTIFF224 to 5,093May 26, 2015run Aug 14, 2011

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.