OPERATORS · TEXAS · P-5 NUMBER 30121 · ATASCOSA COUNTY

Argyle Drilling Company, Inc. in Atascosa 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.

Argyle Drilling Company, INC. has 8 drilling permits on file in Atascosa County, the first issued in 1985 and the latest on December 3, 1985.

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
8
permits, all time since 1985
—
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 · ATASCOSA ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Dec 3, 1985Webb, Tommy C. "B" #11A 291631Drill1,900
Nov 15, 1985Webb, Tommy C. "B" #12A 290081Drill1,900
Sep 9, 1985Webb, Tommy C. "B" #8A 284298Drill1,900
Sep 4, 1985Webb, Tommy C. "B" #10A 283638Drill1,900
Sep 4, 1985Webb, Tommy C. "B" #14A 283645Drill1,900
Sep 4, 1985Webb, Tommy C. "B" #16A 283644Drill1,900
Sep 4, 1985Webb, Tommy C. "B" #18A 283647Drill1,900
Sep 4, 1985Webb, Tommy C. "B" #6A 283641Drill1,900

All 8 permits in Atascosa County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 8

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 Atascosa 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/30121/counties/atascosa, documented in the API reference.