WELL · 42-237-37469 · DISTRICT 9

Persimmon #1

Plugged

Jack County · Plemons (Conglomerate) field  · Vertical

Persimmon #1 (API 42-237-37469) is a plugged well in Jack County, plugged July 10, 2006, last operated by Eog Resources Inc..

The RRC has issued one drilling permit (amended twice), issued January 29, 1988, permitted to 5,400 ft.

It was permitted by Hunter Exploration CO. and has since transferred to Eog Resources Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Caddo, Marble Falls.

Its lease has reported 10.5K barrels of oil and 102K mcf of gas since January 1993, last reporting in September 2006.

Operator of record

EOG Resources Inc.

Permitted by Hunter Exploration Co.; the EWA schedule now lists a different operator.

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

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reports3-R Production, Inc.through Oct 2003
Latest permitHunter Exploration Co.Jan 29, 1988

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

5,400
total depth, ft
3
permits on file
Jan 29, 1988
last permit issued
Mar 24, 1988
completed
10.5K
cumulative oil, bbl
102K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Sep 2006

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 24, 1988
Shut in
—
Plugged
Jul 10, 2006

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Persimmon O-13-27428Plemons (Conglomerate)EOG Resources, Inc.110.5K102KJan 1993 – Sep 2006

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.

  1. 13-R Production, Inc.Jan 1993 → Oct 2003

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
341942-97Field transferHunter Exploration Co.Feb 27, 1989Jan 29, 1988—5,400
341942-98DrillHunter Exploration Co.Apr 4, 1988Jan 29, 1988—5,400
341942-99DrillHunter Exploration Co.Jan 27, 1988Jan 29, 1988—5,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-27428————

Formation tops

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

FormationMD ftSubsea
Caddo4,402-3,108
Marble Falls4,894-3,600

Perforations

Perforated and open-hole intervals.

FromToType
4,7544,762Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62541212.25230 S
4.54,9307.875150 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
00Jul 7, 1989Feb 24, 1989—
00Jun 7, 1989——
00Jun 7, 1988Apr 4, 1988Yes
00May 19, 1988——

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