OPERATORS · TEXAS · P-5 NUMBER 48940 · YOUNG COUNTY

Barbee & Co., Inc. in Young 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.

Barbee & Co., INC. has 14 drilling permits on file in Young County, the first issued in 1982 and the latest on February 12, 1985.

None were issued in the last twelve months.

It is operator of record on 1 wells in the county: 0 producing, 0 shut in, 0 injection.

Its completed wells here most often report Atoka, Caddo, Marble Falls.

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

Permits issued by month

LAST FIVE YEARS · YOUNG ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Feb 12, 1985Boozer/State #2 266702Drill5,000
Dec 3, 1984Roach, G. H. #1 260083Drill5,000
Sep 5, 1984Boozer, John #1 250836Drill5,000
Aug 28, 1984Boozer #4 249893Drill5,000
Apr 17, 1984Allar #1 236100Drill5,000
Apr 6, 1984Boozer - State Unit #1 234859Drill5,000
Mar 26, 1984Boozer #3 233484Drill4,469
Feb 14, 1984Stewart, Mary B. #1 229342Drill4,969
Nov 15, 1983Burgess #1A 220597Drill4,969
Aug 30, 1983Burgess #2 208523Drill2,999

All 14 permits in Young County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 14

12 MONTHS / ALL TIME

Formations reported

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 Young 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/48940/counties/young, documented in the API reference.