WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-181-00554

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-181-00554Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Ramp #142-181-31400Grayson, TX · Silver Creek Oil & Gas LLC0.57RESISTIVITYTIFF1,624 to 8,000Sep 29, 2008run Jul 19, 2005
Sadler /Penn./ Field Unit #4HHZ42-181-31573Grayson, TX · Silver Creek Oil & Gas LLC0.64Measure While Drilling (MWD)14 TIFF6,275 to 9,180Oct 23, 2018
Marshall John #442-181-30202Grayson, TX · Silver Creek Oil & Gas LLC0.77NEUTRON/DENSITY POROSITYTIFF6,500 to 7,886Sep 11, 2009run Oct 18, 2004
John Marshall #6HHZ42-181-31499Grayson, TX · Silver Creek Oil & Gas LLC0.87RESISTIVITYTIFF8,641 to 10,497Sep 9, 2015run Sep 17, 2012
Sandusky /Oil Creek Sd./ Unit #90542-181-00118Grayson, TX · Silver Creek Oil & Gas LLC1.11RESISTIVITYTIFF7,004 to 7,664Sep 29, 2008run Jun 18, 2005
Sadler /Penn./ Field Unit #2HHZ42-181-31550Grayson, TX · Silver Creek Oil & Gas LLC1.16Measure While Drilling (MWD)LAS + TIFF6,000 to 10,489Jul 21, 2017
John Marshall #742-181-31624Grayson, TX · Silver Creek Oil & Gas LLC1.17ResistivityLAS + TIFF1,575 to 6,557Jun 9, 2025
North Sadler Penn Unit #1HHZ42-181-31530Grayson, TX · Silver Creek Oil & Gas LLC1.30RESISTIVITYTIFF5,671 to 10,733Aug 25, 2016run Aug 11, 2013
Lilly Unit #1HHZ42-181-31519Grayson, TX · Silver Creek Oil & Gas LLC1.41RESISTIVITYTIFF6,880 to 11,153Aug 25, 2016run Jun 4, 2013
M.A. Scarbrough #842-181-31508Grayson, TX · Silver Creek Oil & Gas LLC1.46NEUTRON/DENSITY POROSITYTIFF1,557 to 7,955Sep 2, 2015run Aug 26, 2012
Renfro Unit #1HHZ42-181-31559Grayson, TX · Silver Creek Oil & Gas LLC1.59Measure While Drilling (MWD)LAS + TIFF1,537 to 8,010Nov 20, 2017
Hunt #142-181-31518Grayson, TX · Silver Creek Oil & Gas LLC1.63COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITY2 TIFF1,637 to 7,804Dec 27, 2013run May 5, 2013
Baum #142-181-31517Grayson, TX · Atoka Operating Inc.1.80COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF6,850 to 7,876May 17, 2016run Apr 24, 2013
Baum #142-181-31517Grayson, TX · Atoka Operating Inc.1.80RESISTIVITYTIFF1,698 to 7,876May 17, 2016run Apr 24, 2013
Hawthorne #2HHZ42-181-31558Grayson, TX · Silver Creek Oil & Gas LLC1.80Measure While Drilling (MWD)LAS + TIFF7,125 to 10,424Sep 15, 2017
Swink Unit #2HHZ42-181-31534Grayson, TX · Silver Creek Oil & Gas LLC1.81RESISTIVITYTIFF7,340 to 11,258Nov 11, 2016run Sep 25, 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.