WELL · 42-177-34480 · DISTRICT 1

Parton H #8H

Y

Gonzales County · Eagleville (Eagle Ford-1) field · Producing  · Horizontal

Parton H #8H (API 42-177-34480) is a horizontal well in Gonzales County operated by Eog Resources Inc., completed September 19, 2022 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 25, 2022, permitted to 11,300 ft.

Completion filings report 9 formation tops, including Reklaw, Wilcox, Carrizo, Navarro.

Its lease has reported 226K barrels of oil and 146K mcf of gas since September 2022, last reporting in July 2026.

Operator of record

EOG Resources Inc.

Midland, TX · P-5 Y, filed Jul 4, 2026 · 16,348 permits on file · (713) 594-5431

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Apr 2026
Latest permitEOG Resources, Inc.Feb 25, 2022
11,300
total depth, ft
1
permits on file
Feb 25, 2022
last permit issued
Sep 19, 2022
completed
226K
cumulative oil, bbl
146K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2022 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 19, 2022
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

29.210788, -97.599283

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Gonzales County.

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Parton H O-1-20755Eagleville (Eagle Ford-1)EOG Resources, Inc.1226K146KSep 2022 – Jul 2026

Oil, barrels lease total

Last 12 months 27,562 · prior 12 38,166(-28%)

05K10K202420252026

Gas, mcf lease total

Last 12 months 15,035 · prior 12 24,266(-38%)

05K10K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1EOG Resources, Inc.Sep 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
877260-99DrillEOG Resources, Inc.Feb 18, 2022Feb 25, 2022May 15, 202211,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-20755————

Formation tops

As filed on W-2/G-1. Subsea from 310 ft elevation.Download CSV →

FormationMD ftSubsea
Reklaw2,735-2,425
WilcoxWILCOX - DISPOSAL3,310-3,000
Carrizo3,370-3,060
Navarro7,538-7,228
Anacacho9,113-8,803
Austin ChalkAUSTIN CHALK - H2S9,362-9,052
Eagle FordEAGLE FORD - H2S9,653-9,343
BudaBUDA - H2S, DISPOSAL——
EdwardsEDWARDS - H2S——

Perforations

Perforated and open-hole intervals.

FromToType
9,96115,932Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,67712.251,559 S
615,9178.51,730 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Nov 3, 2022Oct 6, 2022Yes

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.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Parton G42-177-34479

0.0 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,735-2,425
Wilcox3,310-3,000
Carrizo3,370-3,060
Navarro7,553-7,243
Anacacho9,131-8,821
Austin Chalk9,370-9,060
Eagle Ford9,668-9,358
Buda—

9 TOPS · FIRST 8

Parton F42-177-34478

0.0 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,610-2,300
Wilcox3,185-2,875
Carrizo3,245-2,935
Navarro7,595-7,285
Anacacho9,134-8,824
Austin Chalk9,372-9,062
Eagle Ford9,668-9,358
Edwards—

9 TOPS · FIRST 8

Parton E42-177-34477

0.0 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,610-2,300
Wilcox3,185-2,875
Carrizo3,245-2,935
Navarro7,595-7,285
Anacacho9,160-8,850
Austin Chalk9,399-9,089
Eagle Ford9,686-9,376
Edwards—

9 TOPS · FIRST 8

Parton C42-177-34249

0.5 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,610-2,289
Wilcox3,185-2,864
Carrizo3,245-2,924
Navarro7,591-7,270
Anacacho9,193-8,872
Austin Chalk9,439-9,118
Eagle Ford9,739-9,418
Buda—

9 TOPS · FIRST 8

Parton B42-177-34248

0.5 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,610-2,289
Wilcox3,185-2,864
Carrizo3,245-2,924
Navarro7,590-7,269
Anacacho9,203-8,882
Austin Chalk9,447-9,126
Eagle Ford9,747-9,426
Edwards—

9 TOPS · FIRST 8

Parton A42-177-34247

0.5 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,610-2,289
Wilcox3,185-2,864
Carrizo3,245-2,924
Navarro7,592-7,271
Anacacho9,223-8,902
Austin Chalk9,455-9,134
Eagle Ford9,754-9,433
Buda—

9 TOPS · FIRST 8

Fogerty Unit42-177-34245

0.5 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,610-2,289
Wilcox3,185-2,864
Carrizo3,245-2,924
Navarro7,593-7,272
Anacacho9,216-8,895
Eagle Ford9,756-9,435
Austin Chalk—
Edwards—

9 TOPS · FIRST 8

Fogerty Unit42-177-33931

0.8 KM · EOG Resources, Inc. · Section with this well →

Reklaw2,625-2,280
Wilcox3,200-2,855
Carrizo3,260-2,915
Navarro7,453-7,108
Anacacho9,237-8,892
Austin Chalk9,484-9,139
Eagle Ford9,777-9,432
Edwards—

9 TOPS · FIRST 8

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/17734480, documented in the API reference.