WELL · 42-175-34107 · DISTRICT 2
Rush #1
Goliad County · Vertical
Rush #1 (API 42-175-34107) is a permitted well in Goliad County filed by Hurd Enterprises, Ltd.; no completion report is on file yet.
The RRC has issued 2 drilling permits between 2008 and 2010, permitted to 14,500 ft.
Completion filings report one formation top, including Wilcox.
Operator of record
San Antonio, TX · P-5 Y, filed Mar 4, 2026 · 261 permits on file · (361) 816-6461
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Marwell Petroleum Ltd Partnrshipthrough Apr 2026 |
| Latest permit | Hurd Enterprises, Ltd.Nov 4, 2010 |
- 14,500
- total depth, ft
- 2
- permits on file
- Nov 4, 2010
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 344K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2009 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 |
|---|---|---|---|---|---|---|
| Rush, D.M. G-2-256844 | Wildcat | Marwell Petroleum Ltd Partnrship | 1 | 0 | 344K | Jul 2009 – Jul 2026 |
Gas, mcf lease total
Last 12 months 8,278 · prior 12 10,270(-19%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Hurd Enterprises, Ltd.Jul 2010 → Apr 2021
- 2Marwell Petroleum Ltd PartnrshipMay 2021 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 703946-99 | Recompletion | Hurd Enterprises, Ltd. | Oct 18, 2010 | Nov 4, 2010 | — | 14,500 |
| 666579-99 | Drill | Tempest Energy Resources, LP | Jul 11, 2008 | Aug 5, 2008 | Sep 17, 2008 | 14,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-256844 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 161 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| WilcoxTOP OF WILCOX | 10,120 | -9,959 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,120 | 10,130 | Perforated |
| 10,196 | 10,211 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 2,800 | 17.5 | 1,870 S |
| 9.625 | 9,950 | 12.25 | 840 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 | Aug 26, 2011 | Jan 21, 2010 | — |
| 00 | Jul 13, 2011 | Dec 16, 2009 | Yes |
| 00 | Aug 11, 2010 | — | — |
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-175-34107 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-175-34107 → 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/17534107, documented in the API reference.