TEXAS · WELLS · KARNES COUNTY · API 42-255-31617 · DISTRICT 02

Milton Unit #2

Shut in

Karnes County · Eagleville (Eagle Ford-2) field · Observation  · Vertical

Milton Unit #2 (API 42-255-31617) is a well in Karnes County operated by Eog Resources Inc., completed August 16, 2009 and listed as observation on the RRC schedule, shut in February 1, 2026.

The RRC has issued one drilling permit, issued July 23, 2009, permitted to 10,760 ft.

Its 2 leases have reported 2.89M barrels of oil and 5.01M mcf of gas since April 2009, last reporting in July 2026. The leases carry 25 wells, so these are lease totals, not this well alone.

Operator of record

EOG Resources Inc.

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 scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Apr 2026
Latest permitEOG Resources, Inc.Jul 23, 2009
10,760
total depth, ft
1
permits on file
Jul 23, 2009
last permit issued
Aug 16, 2009
completed
2.89M
cumulative oil, bbl
5.01M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 16, 2009
Shut in
Feb 1, 2026
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 25 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Milton Unit O-2-9512Eagleville (Eagle Ford-2)EOG Resources, Inc.192.71M4.81MDec 2010 – Jul 2026
Milton Unit O-2-9333Eagleville (Eagle Ford)EOG Resources, Inc.6177K196KApr 2009 – Sep 2011

Oil, barrels lease total

Last 12 months 40,529 · prior 12 44,853(-10%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 185,632 · prior 12 149,119(+24%)

020K40K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.Apr 2009 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
683391-99DrillEOG Resources, Inc.Jul 23, 2009Jul 23, 2009Aug 3, 200912,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 16, 2009Milton Unit O-2-9512Eagleville (Eagle Ford-2)EOG Resources Inc.Observation · shut in Feb 1, 202610,760
Aug 16, 2009Milton Unit O-2-9333Eagleville (Eagle Ford)EOG Resources Inc.Not on Schedule—
Aug 16, 2009Milton Unit O-2-9512Eagleville (Eagle Ford-2)EOG Resources Inc.Not on Schedule—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,12012.251,425 S
5.510,7558.751,625 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
00Mar 16, 2011Apr 14, 2010—
00Nov 29, 2010Apr 14, 2010—
00May 25, 2010Oct 23, 2009Yes
00Feb 25, 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.

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