OPERATORS · TEXAS · P-5 NUMBER 647281 · PECOS COUNTY

Pearl Resources Operating Co.llc in Pecos 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.

Pearl Resources Operating Co.LLC has 7 drilling permits on file in Pecos County, the first issued in 2013 and the latest on December 31, 2018.

None were issued in the last twelve months.

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

Its completed wells here most often report Yates, Queen, Rustler.

0
permits, 12 months
7
permits, all time since 2013
—
horizontal, 12 months
—
ft average depth, 12 months
5
wells of record
2
producing · 3 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · PECOS ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Dec 31, 2018Garnet State #2211HD 840765DrillHZ15,000
Dec 31, 2018Garnet State #2022HA 840541DrillHZ15,000
Dec 31, 2018Garnet State #2021HA 840451DrillHZ15,000
Sep 9, 2016Garnet State #4 818111Drill13,500
Jul 19, 2016Garnet State #3 817026Drill16,000
Jun 20, 2016Garnet State #1 816421Drill16,000
Feb 20, 2013Brandenburg #1 756827Recompletion17,647
Oct 26, 1979Brandenburg #1 62099Drill19,000

All 7 permits in Pecos County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 6
Recompletion
0 / 1

12 MONTHS / ALL TIME

Leases it reports here

LeaseWellsOil, bblLast reported
Brandenburg123.3KJul 2026
Garnet State45.81KJul 2026
Brandenburg10May 2013

All leases it reports → ·  Other operators in Pecos 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/647281/counties/pecos, documented in the API reference.