WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-399-32089

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-399-32089Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Cree Sykes #1206__42-399-35004Runnels, TX · Pioneer Exploration Ltd.0.83ResistivityTIFFARRAY INDUCTION GAMMA RAY SP100 to 4,131Feb 27, 2007run Dec 5, 2006
Johnson John J. #142-399-34959Runnels, TX · Baker Operating Inc.0.97RESISTIVITYTIFF170 to 4,603Jun 25, 2009run Jun 12, 2006
Cree Sykes Unit #120542-399-35003Runnels, TX · Atlas Operating LLC1.04RESISTIVITYTIFF100 to 4,088Oct 19, 2009run Oct 21, 2006
Kurtz #142-399-35542Runnels, TX · Window Operating Co. The1.20RESISTIVITYTIFF100 to 4,562Jun 25, 2018run Apr 17, 2018
Dobbins #142-399-33311Runnels, TX · B & M Operating LLC1.38NEUTRON/DENSITY POROSITYTIFF3,496 to 4,514Apr 5, 2011run Aug 10, 2007
Dobbins #142-399-33311Runnels, TX · B & M Operating LLC1.38RESISTIVITYTIFF450 to 4,516Apr 5, 2011run Aug 10, 2007
Cree Sykes Unit #1331__42-399-35030Runnels, TX · Pioneer Exploration Ltd.1.41ResistivityTIFFARRAY INDUCTION TOOL SP GAMMA RAY40 to 4,043Jun 26, 2007run Feb 24, 2007
Davenport #142-399-35541Runnels, TX · Window Operating Co. The1.48RESISTIVITYTIFF2,200 to 4,344Jun 25, 2018run Apr 9, 2018
White W. W. #1__42-399-35391Runnels, TX · Byrne Oil Company1.48RESISTIVITYTIFF2,150 to 4,142Mar 30, 2015run Jun 18, 2013
Cree Sykes Unit #100342-399-35129Runnels, TX · Atlas Operating LLC1.48RESISTIVITYTIFF50 to 4,134Jul 19, 2011run Jul 29, 2008
Cree Sykes Unit #132842-399-35015Runnels, TX · Atlas Operating LLC1.70RESISTIVITYTIFF50 to 4,725Dec 23, 2009run Dec 31, 2006
Cree Sykes Unit #132942-399-35016Runnels, TX · Atlas Operating LLC1.73RESISTIVITYTIFF100 to 4,717Dec 22, 2009run Dec 12, 2006
Cree Sykes Unit #132742-399-35013Runnels, TX · Atlas Operating LLC1.78RESISTIVITYTIFF100 to 4,768Nov 24, 2009run Nov 19, 2006
Cree Sykes Unit #703442-399-34967Runnels, TX · Atlas Operating LLC1.85RESISTIVITYTIFF181 to 4,738Oct 19, 2009run Oct 15, 2006
Cree Sykes Unit #133042-399-35026Runnels, TX · Atlas Operating LLC1.88RESISTIVITYTIFF3,800 to 4,044Jan 20, 2010run Jan 18, 2007
Cree Sykes Unit #702942-399-34944Runnels, TX · Atlas Operating LLC1.91RESISTIVITYTIFF50 to 4,172Apr 30, 2009run Apr 13, 2006
Grohman #142-399-34943Runnels, TX · Atlas Operating LLC1.93RESISTIVITYTIFF50 to 4,316Apr 30, 2009run Apr 10, 2006
Cree Sykes Unit #703242-399-34956Runnels, TX · Atlas Operating LLC1.98RESISTIVITYTIFF100 to 4,731Jun 19, 2009run Jun 3, 2006

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.