OPERATORS · TEXAS · P-5 NUMBER 337293 · CONCHO COUNTY

Guffey, Wm. R. in Concho County

One operator, one county: its permits, wells of record, formations, and leases here, with the rest of the county and the rest of the operator one click away.

Guffey, Wm. R. has 54 drilling permits on file in Concho County, the first issued in 1995 and the latest on March 25, 2015.

None were issued in the last twelve months.

It is not operator of record on any well in the county on the current wellbore schedule.

0
permits, 12 months
54
permits, all time since 1995
—
horizontal, 12 months
—
ft average depth, 12 months
0
wells of record
0
producing · 0 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · CONCHO ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Mar 25, 2015Don Pfluger #1 804922Drill2,350
Jan 26, 2012Pfluger #1 732090Drill2,100
Aug 3, 2011Sorrell 'C' #6 721185Drill2,350
Feb 7, 2011Bunger/Sorrell "a" Unit #1 709221Drill2,350
Oct 29, 2010Shipman/Franklin Unit #1 704123Drill2,350
Aug 9, 2010Sorrell "C" #5 700135Drill2,350
May 7, 2010Schumann "B" #1 695371Drill3,700
Jan 14, 2010Sorrell "C" #4 689516Drill2,350
Sep 23, 2009Sorrell "C" #3 685423Drill2,350
Aug 13, 2009Cunningham #1 683160Drill2,900

All 54 permits in Concho County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 54

12 MONTHS / ALL TIME

Formations reported

No completion tops on file for its wells here.

Leases it reports here

No leases with wells completed in this county carry this operator's production reports.

All leases it reports → ·  Other operators in Concho County →

About this data

Permits from the RRC OGA049M master and daily daf420 files; wells of record and status from the EWA wellbore schedule, weekly; formations from the dbf900 wellbore file; leases from PDQ lease reports, placed in the county by the wells completed on them.

Developers: this page as JSON is GET /v1/data/operators/tx/337293/counties/concho, documented in the API reference.