WELL · 42-009-34155 · DISTRICT 9

Hargraves #6

Plugged

Archer County · Archer County Regular field  · Vertical

Hargraves #6 (API 42-009-34155) is a plugged well in Archer County, plugged February 8, 2007, last operated by Shawver & Shawver.

The RRC has issued one drilling permit, issued January 17, 1980, permitted to 1,500 ft.

It was permitted by Farmer, Lewis & Hayden and has since transferred to Shawver & Shawver on the wellbore schedule.

Its lease has reported 1.08K barrels of oil and 26 mcf of gas since January 1993, last reporting in March 2008. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Shawver & Shawver

Permitted by Farmer, Lewis & Hayden; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Oct 4, 2025 · 4 permits on file · (940) 782-0773

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleShawver & Shawver
Production reportsShawver & Shawverthrough Mar 1996
Latest permitFarmer, Lewis & HaydenJan 17, 1980

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

1,500
total depth, ft
1
permits on file
Jan 17, 1980
last permit issued
Jan 21, 1984
completed
1.08K
cumulative oil, bbl
26
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 21, 1984
Shut in
—
Plugged
Feb 8, 2007

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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hargraves O-13-23616Archer County RegularShawver & Shawver31.08K26Jan 1993 – Mar 2008

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. 1Shawver & ShawverJan 1993 → Mar 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
69987-99DrillFarmer, Lewis & HaydenJan 17, 1980Jan 17, 1980Mar 10, 19801,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-23616————

Perforations

Perforated and open-hole intervals.

FromToType
1,2571,263Perforated
1,2761,282Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,4637.875200 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
00Oct 22, 1984Sep 18, 1984—
00Oct 5, 1984——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
524K
bbl, all reported
Dec 2006
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000050809H-1 InjectionPlugged Mar 22, 2007001,257–0

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120052006

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