OPERATORS · TEXAS · P-5 NUMBER 170037 · WILBARGER COUNTY
Comstock Energy, LLC in Wilbarger 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.
Comstock Energy, LLC has 4 drilling permits on file in Wilbarger County, the first issued in 2013 and the latest on May 27, 2016.
None were issued in the last twelve months.
It is operator of record on 3 wells in the county: 0 producing, 0 shut in, 0 injection.
- 0
- permits, 12 months
- 4
- permits, all time since 2013
- —
- horizontal, 12 months
- —
- ft average depth, 12 months
- 3
- wells of record
- 0
- producing · 0 shut in · 0 injection
Permits issued by month
LAST FIVE YEARS · WILBARGER ONLY
Last 12 months 0 · prior 12 0
Latest permits here
| Issued | Lease / well | Type | Depth |
|---|---|---|---|
| May 27, 2016 | W.T. Waggoner Est A #14 815171 | Drill | 4,250 |
| Jan 23, 2015 | W.T. Waggoner Estate 'A' #1CH 772425 | DrillHZ | 4,100 |
| May 6, 2014 | W.T. Waggoner Estate 'A' #12 784724 | Drill | 4,200 |
| Oct 9, 2013 | Waggoner, W.T. Estate 'N' #1 768697 | Recompletion | 4,610 |
| Mar 23, 2005 | Waggoner, W. T. Estate N #2 555760 | RecompletionHZ | 4,065 |
All 4 permits in Wilbarger County, searchable → · Wells of record here →
Permit types and formations
Permit types
- Drill
- 0 / 3
- Recompletion
- 0 / 1
12 MONTHS / ALL TIME
Formations reported
No completion tops on file for its wells here.
Leases it reports here
| Lease | Wells | Oil, bbl | Last reported |
|---|---|---|---|
| Waggoner, W. T., Estate -N- | 3 | 26.3K | Jan 2026 |
All leases it reports → · Other operators in Wilbarger 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/170037/counties/wilbarger, documented in the API reference.