WELL · 42-167-31529 · DISTRICT 3
Mercury #1
Galveston County · High Island field · Shut IN · Vertical
Mercury #1 (API 42-167-31529) is a well in Galveston County operated by Esco Oil Operating Company LLC, completed August 15, 2016 and listed as shut in on the RRC schedule.
The RRC has issued one drilling permit, issued May 20, 2016, permitted to 5,500 ft.
Completion filings report 4 formation tops, including Pliocene - Disposal, Miocene (undifferentiated), Frio, San Miguel.
No lease production has been reported under this well’s leases.
Operator of record
Esco Oil Operating Company LLC
Houston, TX · P-5 Y, filed Sep 4, 2025 · 33 permits on file · (281) 235-2627
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Esco Oil Operating Company LLC |
| Production reports | none |
| Latest permit | Esco Oil Operating Company LLCMay 20, 2016 |
- 5,500
- total depth, ft
- 1
- permits on file
- May 20, 2016
- last permit issued
- Aug 15, 2016
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 2018 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Aug 15, 2016
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: S
Surface location
No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH APR 2026
Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Mercury O-3-27714 | High Island | Esco Oil Operating Company LLC | 1 | 0 | 0 | May 2018 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 815709-99 | Drill | Esco Oil Operating Company LLC | May 17, 2016 | May 20, 2016 | Jul 24, 2016 | 5,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-3-27714 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 10 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Pliocene - Disposal | 3,815 | -3,805 |
| Miocene (undifferentiated)MIOCENE - DISPOSAL | 4,453 | -4,443 |
| FrioFRIO - DISPOSAL | — | — |
| San MiguelSAN MIGUEL - DISPOSAL | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,547 | 3,553 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 790 | 12.25 | 397 S |
| 5.5 | 4,800 | 7.875 | 490 S |
Completion filings
W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 22, 2020 | Feb 12, 2020 | Yes |
The source documents
Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.
- Wellbore filings for 42-167-31529 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-167-31529 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
About this data
Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.
New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease
Developers: this page as JSON is GET /v1/data/wells/16731529, documented in the API reference.