TEXAS · WELLS · KARNES COUNTY · API 42-255-31629 · DISTRICT 02
Harper Unit #2H
Karnes County · Eagleville (Eagle Ford-2) field · Shut In · Horizontal
Harper Unit #2H (API 42-255-31629) is a horizontal well in Karnes County operated by Eog Resources Inc., completed March 21, 2010 and listed as shut in on the RRC schedule, shut in June 1, 2020.
The RRC has issued one drilling permit (amended once), issued October 22, 2009, permitted to 10,529 ft.
Completion filings report 5 formation tops, including Midway, Navarro, Olmos, Anachacho.
Its 2 leases have reported 4.31M barrels of oil and 9.32M mcf of gas since October 2009, last reporting volume in April 2026. The leases carry 32 wells, so these are lease totals, not this well alone.
Operator of record
- Based in
- Midland, TX
- P-5 status
- Active (A)
- P-5 last filed
- Oct 2, 2025
- Permits on file
- 16,354
- Phone
- (713) 651-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | EOG Resources Inc. |
| Production reports | EOG Resources, Inc.through Apr 2026 |
| Latest permit | EOG Resources, Inc.Oct 22, 2009 |
- 10,529
- total depth, ft
- 2
- permits on file
- Oct 22, 2009
- last permit issued
- Mar 21, 2010
- completed
- 4.31M
- cumulative oil, bbl
- 9.32M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2010 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Mar 21, 2010
- Shut in
- Jun 1, 2020
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (X)
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 2 leases this well is completed on; they carry 32 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Harper Unit O-2-9508 | Eagleville (Eagle Ford-2) | EOG Resources, Inc. | 23 | 4.05M | 9.02M | Dec 2010 – Apr 2026 |
| Harper Unit O-2-9379 | Eagleville (Eagle Ford) | EOG Resources, Inc. | 9 | 251K | 297K | Oct 2009 – Nov 2010 |
Oil, barrels lease total
Last 12 months 75,561 · prior 12 87,337(-13%)
Gas, mcf lease total
Last 12 months 289,962 · prior 12 347,641(-17%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1EOG Resources, Inc.Jan 2010 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 686404-98 | Drill | EOG Resources, Inc. | Dec 2, 2009 | Oct 22, 2009 | Dec 17, 2009 | 12,000 |
| 686404-99 | Drill | EOG Resources, Inc. | Oct 21, 2009 | Oct 22, 2009 | Dec 18, 2009 | 12,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Mar 21, 2010 | Harper Unit O-2-9508 | Eagleville (Eagle Ford-2) | EOG Resources Inc. | Shut In · shut in Jun 1, 2020 | 10,529 |
| Mar 21, 2010 | Harper Unit O-2-9379 | Eagleville (Eagle Ford) | EOG Resources Inc. | Not on Schedule | — |
| — | Harper Unit O-2-9379 | Eagleville (Eagle Ford) | EOG Resources Inc. | Not on Schedule | — |
Formation tops
As filed on W-2/G-1. Subsea from 308 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Midway | 6,698 | -6,390 |
| Navarro | 7,628 | -7,320 |
| Olmos | 8,418 | -8,110 |
| Anachacho | 9,790 | -9,482 |
| Eagle FordEAGLEFORD | 10,410 | -10,102 |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 4,325 | 12.25 | 1,370 S |
| 5.5 | 10,529 | 8.75 | 2,025 S |
| 5.5 | 12,485 | 8.75 | 2,025 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Mar 16, 2011 | May 13, 2010 | — |
| 00 | Sep 17, 2010 | May 13, 2010 | — |
| 00 | Jun 18, 2010 | Feb 17, 2010 | Yes |
| 00 | Apr 9, 2010 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Feb 12, 2013. Resistivity. 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.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans Midway, Navarro, Olmos, Anachacho | TIFF | 4,319 to 10,268 | Feb 12, 2013run Dec 28, 2009 | 0.90 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-255-31629 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-255-31629 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/25531629, documented in the API reference.