WELL LOGS · UNITED STATES · ONE ROW PER LOG

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

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-34262Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Barron #1S_42-363-35827Palo Pinto, TX · Slate Holdings Inc.1.13NEUTRON/DENSITY POROSITYTIFF140 to 1,984Feb 20, 2009run Oct 31, 2008
Barron #1S_42-363-35827Palo Pinto, TX · Slate Holdings Inc.1.13RESISTIVITYTIFF120 to 2,004Feb 20, 2009run Oct 31, 2008
Mitchell #1 C42-363-35560Palo Pinto, TX · Borderline Operating Corp.1.18RESISTIVITYTIFF335 to 3,583Nov 2, 2009run Jul 22, 2006
Harlin #142-363-35534Palo Pinto, TX · Reval Exploration LLC1.18ResistivityTIFFDUAL INDUCTION FOCUSED GAMMA RAY LOG330 to 3,620Oct 18, 2007run May 17, 2006
Stoner #142-363-35671Palo Pinto, TX · Sabre Oil and Gas Corp.1.23ResistivityTIFFDUAL INDUCTION FOCUSED GAMMA RAY LOG100 to 1,804Feb 11, 2008run Aug 30, 2007
Barron #142-363-35350Palo Pinto, TX · T & S Oil & Gas LLC1.33NEUTRON/DENSITY POROSITYTIFF280 to 1,250Aug 15, 2008run Mar 1, 2005
Barron #342-363-35358Palo Pinto, TX · T & S Oil & Gas LLC1.33RESISTIVITYTIFF250 to 3,841Aug 15, 2008run Mar 15, 2005
Barron #742-363-35446Palo Pinto, TX · T & S Oil & Gas LLC1.45COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF40 to 551Nov 19, 2008run Nov 9, 2005
Barron #242-363-35357Palo Pinto, TX · T & S Oil & Gas LLC1.51ACOUSTIC POROSITYTIFF260 to 3,823Sep 25, 2008run Jun 23, 2005
Butler #142-363-35690Palo Pinto, TX · Corda Corporation1.56RESISTIVITYTIFF0 to 3,405Jan 30, 2009run Oct 25, 2007
Nichols #142-363-35746Palo Pinto, TX · McCown Engineering1.70RESISTIVITYTIFF170 to 3,500Mar 7, 2011run Feb 28, 2008
Barron #542-363-35428Palo Pinto, TX · T & S Oil & Gas LLC1.71NEUTRON POROSITYTIFF30 to 3,393Oct 15, 2008run Oct 1, 2005
Barron #642-363-35432Palo Pinto, TX · T & S Oil & Gas LLC1.88NEUTRON/DENSITY POROSITYTIFF1,658 to 3,795Oct 30, 2008run Oct 8, 2005
Williams #142-363-35424Palo Pinto, TX · North Texas Plugging LLC1.93NEUTRON/DENSITY POROSITYTIFF269 to 3,523Oct 16, 2008run Sep 12, 2005
Williams #142-363-35424Palo Pinto, TX · North Texas Plugging LLC1.93RESISTIVITYTIFF269 to 3,523Oct 16, 2008run Sep 12, 2005
Barron #942-363-35494Palo Pinto, TX · T & S Oil & Gas LLC1.93RESISTIVITYTIFF260 to 3,793Feb 5, 2009run Jan 26, 2006
Keck #142-363-35415Palo Pinto, TX · Laws Exploration LLC1.94NEUTRON/DENSITY POROSITYTIFF270 to 3,859Oct 15, 2008run Sep 4, 2005

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.