WELL · 42-493-32576 · DISTRICT 1
Hofferichter Unit #1H
Wilson County · Eagleville (Eagle Ford-1) field · Horizontal
Hofferichter Unit #1H (API 42-493-32576) is a plugged horizontal well in Wilson County, plugged December 13, 2012, last operated by Marathon Oil Company.
The RRC has issued one drilling permit (amended once), issued March 2, 2011, permitted to 12,000 ft.
Completion filings report 3 formation tops, including Austin Chalk, Eagle Ford, Buda.
Its lease has reported 69 barrels of oil since July 2011, last reporting in May 2013.
Operator of record
Houston, TX · P-5 Y, filed Apr 4, 2026 · 3,707 permits on file · (800) 332-9449
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Marathon Oil Company |
| Production reports | Marathon Oil Companythrough Aug 2011 |
| Latest permit | Marathon Oil CompanyMar 2, 2011 |
- 12,000
- total depth, ft
- 2
- permits on file
- Mar 2, 2011
- last permit issued
- Jul 14, 2011
- completed
- 69
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2011 THROUGH May 2013
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jul 14, 2011
- Shut in
- —
- Plugged
- Dec 13, 2012
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 |
|---|---|---|---|---|---|---|
| Hofferichter Unit O-1-15736 | Eagleville (Eagle Ford-1) | Marathon Oil Company | 1 | 69 | 0 | Jul 2011 – May 2013 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Marathon Oil CompanyAug 2011 → Aug 2011
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 711124-98 | Drill | Marathon Oil Company | Apr 3, 2012 | Mar 2, 2011 | Apr 20, 2011 | 12,000 |
| 711124-99 | Drill | Marathon Oil Company | Feb 28, 2011 | Mar 2, 2011 | Apr 20, 2011 | 12,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-15736 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 438 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Austin Chalk | 6,713 | -6,275 |
| Eagle Ford | 6,975 | -6,537 |
| Buda | 7,057 | -6,619 |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 4,315 | 14.5 | 849 S |
| 5.5 | 7,260 | 8.75 | 797 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 | May 3, 2012 | Sep 6, 2011 | 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-493-32576 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-493-32576 → 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/49332576, documented in the API reference.