WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-187-31237

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-187-31237Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Floyd #242-187-33679Guadalupe, TX · Production Resources Inc.0.85OtherTIFF50 to 1,000Jan 16, 2022
Floyd #142-187-33678Guadalupe, TX · Production Resources Inc.0.90Gamma RayTIFF192 to 932Jan 16, 2022
Ball James #742-187-33621Guadalupe, TX · Iron Battalion Energy LLC1.00NEUTRON POROSITYTIFF0 to 788Jul 10, 2016run Jan 2, 2014
Ward #1642-187-33622Guadalupe, TX · Levant Energy LLC1.63NEUTRON POROSITYTIFF0 to 1,250Oct 13, 2014run Jan 9, 2014
Gomo #742-187-33633Guadalupe, TX · ENERGON31.82NEUTRON POROSITYTIFF0 to 803Dec 30, 2016run Jul 27, 2015

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.