Petrora

WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-025-00690

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-025-00690Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Davis #1__42-025-33544Bee, TX · Newfield Exploration Company0.69NEUTRON/DENSITY POROSITYTIFF8,300 to 10,972Feb 20, 2015run Dec 30, 2007
Yoward H. E. #942-025-33622Bee, TX · SRS Properties LLC0.70COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,156 to 11,254Aug 6, 2009run Jan 29, 2009
Goree #142-025-33461Bee, TX · Britanco L.L.C.0.90COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF100 to 11,198Apr 28, 2010run Apr 12, 2007
Yoward-Schramm #1__42-025-33598Bee, TX · Anderson Oil Ltd.1.24COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF8,739 to 11,232Aug 17, 2009run Oct 3, 2008
R. E. Wolters #242-025-33621Bee, TX · Goldston Oil Corporation1.36COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,118 to 10,983Jun 11, 2009run Dec 2, 2008
Shirley #142-025-34020Bee, TX · Dahco Operating LLC1.43InductionTIFF982 to 3,618Jun 24, 2025
Wolters #142-025-33391Bee, TX · Anderson Oil Ltd.1.46COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,114 to 7,834Mar 26, 2009run Mar 30, 2006
Brown Austin #642-025-33454Bee, TX · Vision Oil and Gas LLC1.59COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF2,520 to 11,487Mar 15, 2010run Mar 24, 2007
Luckenbach #142-025-33497Bee, TX · Continental Operating Co.1.62ACOUSTIC POROSITYTIFF2,510 to 11,503Aug 5, 2008run Jul 14, 2007
Langtry-Shirley Trust #142-025-33707Bee, TX · Britanco L.L.C.1.67COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,055 to 4,048May 10, 2011run Mar 31, 2010
Starr-Gunn #142-025-33923Bee, TX · Welderxp Ltd.1.73COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF943 to 4,107Jun 12, 2017run Jun 27, 2014
Austin Brown #7ST42-025-33509Bee, TX · Hughes Dan A. Company L.P.1.75COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF2,502 to 11,404Jan 14, 2015run Aug 15, 2007
Schramm-Nasa #142-025-33470Bee, TX · Continental Operating Co.1.91COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF2,491 to 11,189Oct 4, 2010run Jun 16, 2007
Keller #142-025-33902Bee, TX · Grand Operating Inc.1.98NEUTRON/DENSITY POROSITYTIFF1,193 to 8,609Aug 8, 2017run Jun 3, 2014
West Goree #142-025-33635Bee, TX · Tidal Petroleum Inc.1.99COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF2,515 to 10,613Apr 19, 2010run Apr 9, 2009

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.