WELL · 42-429-32641 · DISTRICT 7

Keith #1

Y

Stephens County · Deann (Conglomerate) field · Producing  · Vertical

Keith #1 (API 42-429-32641) is a well in Stephens County operated by Ray Herring Operating CO. LLC, completed April 26, 1982 and listed as producing on the RRC schedule.

The RRC has issued 2 drilling permits between 1980 and 1982, permitted to 4,253 ft.

It was permitted by Herring, Ray and has since transferred to Ray Herring Operating CO. LLC on the wellbore schedule.

No lease production has been reported under this well’s leases.

Operator of record

Ray Herring Operating Co. LLC

Permitted by Herring, Ray; the EWA schedule now lists a different operator.

Based in
Graham, TX
P-5 status
Active (A)
P-5 last filed
Feb 10, 2026
Permits on file
8
Phone
(940) 549-0370

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHerring Ray
Production reportsRay Herring Operating Co., LLCthrough Mar 2026
Latest permitHerring, RayMay 20, 1982

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

4,253
total depth, ft
2
permits on file
May 20, 1982
last permit issued
Apr 26, 1982
completed
0
cumulative oil, bbl
305K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 26, 1982
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Keith G-8-99906Deann (Conglomerate)Ray Herring Operating Co., LLC10305KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 13,167 · prior 12 15,552(-15%)

01K2K202420252026

Chain of custody

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

  1. 1Herring, RayJan 1993 → Jun 2014
  2. 2Ray Herring EstateJul 2014 → Mar 2016
  3. 3Ray Herring Operating Co., LLCApr 2016 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
161221-99RecompletionHerring, RayMay 20, 1982May 20, 1982—4,400
89626-99DrillHerring, RayAug 12, 1980Aug 12, 1980May 21, 19814,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 26, 1982Keith G-8-99906Deann (Conglomerate)Ray Herring Operating Co. LLCProducing4,253
Nov 2, 1981Keith G-8-96366Johnny (Congl. Upper)Herring RayNot on Schedule—

Perforations

Perforated and open-hole intervals.

FromToType
3,8313,838Perforated
3,8603,865Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62520012.25200 S
2.3753,830——
2.3753,855——
4.54,2537.875260 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
00Jan 12, 1984May 17, 1982—
00Jan 12, 1984Nov 12, 1981—

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