OPERATORS · TEXAS · P-5 NUMBER 847762 · MAVERICK COUNTY

Texas Pipeline LLC in Maverick 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.

Texas Pipeline LLC has 7 drilling permits on file in Maverick County, the first issued in 2010 and the latest on September 16, 2026.

3 of them came in the last twelve months, after none the year before; 0% horizontal, averaging 310 ft.

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

3
permits, 12 months
7
permits, all time since 2010
0%
horizontal, 12 months
310
ft average depth, 12 months
0
wells of record
0
producing · 0 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · MAVERICK ONLY

Last 12 months 3 · prior 12 0

01220222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Sep 16, 2026CP#26-162 Cathodic Protection #44 918665Drill300
Sep 16, 2026Cp# 26-161 #43 918667Drill300
Jun 9, 2026Cp# 26-105 Cathodic Protection #37 916214Drill330
Apr 30, 2019Cathodic Protection #49 852312Drill350
Apr 25, 2019Cathodic Protection #48 852309Drill350
Apr 25, 2019Cathodic Protection #47 852301Drill350
Mar 19, 2010Conoco Rectifier #C000NC 692825Drill190

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

Permit types and formations

Permit types

Drill
3 / 7

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 Maverick 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/847762/counties/maverick, documented in the API reference.