WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-415-31336

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-415-31336Clear

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 16 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Martin Annie #3042-415-34402Scurry, TX · Burk Royalty Co. Ltd.0.08NEUTRON POROSITYTIFF2,100 to 2,518Feb 6, 2009run Jul 28, 2008
Martin Annie #2742-415-34349Scurry, TX · Burk Royalty Co. Ltd.0.25NEUTRON POROSITYTIFF2,100 to 2,563Jul 23, 2008run Dec 13, 2007
Martin Annie #2942-415-34400Scurry, TX · Burk Royalty Co. Ltd.0.43NEUTRON POROSITYTIFF2,100 to 2,522Feb 5, 2009run Jul 30, 2008
Martin Annie #2842-415-34350Scurry, TX · Burk Royalty Co. Ltd.0.50NEUTRON POROSITYTIFF2,100 to 2,538Jul 21, 2008run Dec 10, 2007
Martin T. R. B #2242-415-34554Scurry, TX · Burk Royalty Co. Ltd.0.56NEUTRON POROSITYTIFF1,500 to 2,513Mar 22, 2010run Nov 19, 2009
Martin T. R. B #2142-415-34351Scurry, TX · Burk Royalty Co. Ltd.0.74NEUTRON POROSITYTIFF2,000 to 2,423Jul 21, 2008run Dec 17, 2007
Martin 575 #1HHZ42-415-34921Scurry, TX · Ivory Energy LLC0.97ResistivityTIFF7,200 to 12,500Oct 12, 2018
Martin T. R. #1042-415-04709Scurry, TX · Burk Royalty Co. Ltd.0.99NEUTRON POROSITYTIFF1,800 to 2,602Feb 7, 2011run Oct 7, 1982
Browning #1042-415-34401Scurry, TX · Burk Royalty Co. Ltd.1.04NEUTRON POROSITY2 TIFF2,000 to 2,492Feb 12, 2009run Aug 1, 2008
Browning #1ST42-415-04695Scurry, TX · Burk Royalty Co. Ltd.1.23Neutron PorosityTIFFGAMMA RAY CCL COMP. NEUTRON1,850 to 2,192Mar 28, 2008run Dec 4, 2006
Browning E. G. B #2842-415-34317Scurry, TX · Burk Royalty Co. Ltd.1.39Neutron PorosityTIFFGAMMA RAY CCL COMPENSATED NEUTRON1,700 to 2,298Oct 9, 2007run Jun 1, 2007
Browning E. G. B #2742-415-34228Scurry, TX · Burk Royalty Co. Ltd.1.46Neutron PorosityTIFFGAMMA RAY CCL COMP. NEUTRON1,900 to 2,288Feb 14, 2007run Jun 5, 2006
Fuller #2342-415-35092Scurry, TX · Unitex Oil & Gas L.L.C.1.66RESISTIVITYTIFF400 to 2,904Sep 13, 2017run Aug 29, 2014
CHV-Browning #2542-415-34227Scurry, TX · Burk Royalty Co. Ltd.1.73Neutron PorosityTIFFGAMMA RAY CCL COMPENSATED NEUTRON1,900 to 2,266Feb 14, 2007run Jul 5, 2006
Fuller #2942-415-35470Scurry, TX · Unitex Oil & Gas L.L.C.1.77COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF200 to 2,900Oct 4, 2022run Jul 31, 2019
CHV-Browning #15R42-415-34318Scurry, TX · Burk Royalty Co. Ltd.1.88Neutron PorosityTIFFGAMMA RAY CCL COMPENATED NEUTRON1,450 to 2,284Oct 9, 2007run May 22, 2007

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.