WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-337-33982

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-337-33982Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Brown #3HHZ42-337-33985Montague, TX · EOG Resources Inc.0.13RESISTIVITYTIFF959 to 7,140Sep 9, 2011run Aug 12, 2008
Brown #2HHZ42-337-33984Montague, TX · EOG Resources Inc.0.13SURVEYS CASED HOLETIFF1,200 to 11,240Jun 13, 2011run Mar 28, 2008
Helen Steadham Unit #1HHZ42-337-34508Montague, TX · Scout Energy Management LLC0.57RESISTIVITYTIFF3,995 to 7,700Mar 13, 2014run Feb 14, 2011
Helen Steadham #2HHZ42-337-34509Montague, TX · Scout Energy Management LLC0.66RESISTIVITYTIFF1,400 to 7,640Feb 12, 2014run Feb 17, 2011
Rater Brothers #1HHZ42-337-34568Montague, TX · BKV Barnett II LLC1.24SURVEYS CASED HOLETIFF6,655 to 10,150Mar 31, 2014run Mar 27, 2011
Greenwood Unit #1HHZ42-337-34129Montague, TX · EOG Resources Inc.1.44RESISTIVITYTIFF100 to 7,445Dec 12, 2011run Oct 24, 2008
Walker #4HHZ42-337-34596Montague, TX · Scout Energy Management LLC1.48RESISTIVITY2 TIFF5,000 to 13,549Oct 29, 2014run Oct 8, 2011
Legend #1HHZ42-337-34055Montague, TX · Eagleridge Operating LLC1.60RESISTIVITYTIFF6,000 to 7,870Aug 1, 2011run Jun 27, 2008
Walker #3HHZ42-337-34595Montague, TX · Scout Energy Management LLC1.62RESISTIVITYTIFF5,000 to 13,150Sep 8, 2014run Sep 24, 2011
Caswell 10 #4HHZ42-337-34042Montague, TX · Eagleridge Operating LLC1.63RESISTIVITYTIFF508 to 7,800Jan 31, 2012run Jul 20, 2008
Caswell 10 #4HHZ42-337-34042Montague, TX · Eagleridge Operating LLC1.63RESISTIVITYTIFF6,825 to 9,600Jan 31, 2012run Aug 5, 2008
Charles Reeves #3HHZ42-337-34512Montague, TX · Scout Energy Management LLC1.72OtherTIFF1,400 to 7,640Sep 26, 2022
Charles Reeves #3HHZ42-337-34512Montague, TX · Scout Energy Management LLC1.72RESISTIVITYTIFF1,400 to 7,640Mar 13, 2014run Mar 28, 2011
Walker #2HHZ42-337-34594Montague, TX · Scout Energy Management LLC1.74RESISTIVITYTIFF5,000 to 7,443Sep 5, 2014
Charles Reeves #2HHZ42-337-34511Montague, TX · Scout Energy Management LLC1.80RESISTIVITYTIFF4,600 to 7,480May 19, 2014run Mar 28, 2011
Walker #1HHZ42-337-34598Montague, TX · Scout Energy Management LLC1.85RESISTIVITYTIFF960 to 7,494Sep 5, 2014
Charles Reeves #1HHZ42-337-34510Montague, TX · Scout Energy Management LLC1.93RESISTIVITYTIFF1,100 to 7,414Feb 12, 2014run Mar 28, 2011
Reynolds Unit #1HHZ42-337-34133Montague, TX · BKV Barnett LLC1.95SURVEYS CASED HOLETIFF1,000 to 11,930Nov 15, 2011run Oct 12, 2008
T & T A Unit #1HHZ42-337-34317Montague, TX · BKV Barnett LLC1.98RESISTIVITYTIFF50 to 7,714May 29, 2013run May 2, 2010

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.