OPERATORS · TEXAS · P-5 NUMBER 684631

Quest-Tex Energy Operating, LLC

P-5 status
Delinquent (D)
P-5 last filed
Dec 10, 2013
Based in
Dallas, TX

Quest-Tex Energy Operating, LLC has filed no drilling permits in the past 12 months.

The RRC wellbore file lists 74 wells under its operatorship (1 shut in).

0
permits, last 12 months
—
vs prior 12 months (0)
0
counties, 12 months
0
producing wells, of 80 of record
18
leases reported on · 14 today
—
horizontal, 12 months

WINDOWS ON THE RRC ISSUE DATE · COMPUTED NOV 9, 2026

Permits issued by month

LAST 60 MONTHS · BY ISSUE DATE

Last 12 months 0 · prior 12 0

0120222023202420252026

Counties

No permits on file under this operator number. Counties of its wells of record, from the RRC wellbore file.

CountyWellsProducing
Hutchinson county →57—
Carson county →13—
Gray county →4—

All 0 permits, searchable → · Leases it reported on → · On the map →

Formations in wells it permitted

Tops reported on completion filings for wells permitted under this operator number, including wells others run today. RRC wellbore file. About tops →

FormationWellsPermitted last 3 yrs
No completion tops on file.

Production by month

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Barrels on leases where this operator filed the production report. Lease-level by design; the latest months are revised upward as late reports arrive. From 18 leases it reported on; 4 are reported by other operators today.How production is reported →

0
bbl oil, last 12 reported months
—
vs the 12 months before
0
mcf gas incl. casinghead, last 12
5.19K
bbl oil since reporting began

No lease production reported under this operator number in the last ten years.

Beyond the permit record

RRC wellbore file

Wells of record

80
wells of record on 74 wellbores, 1 on scheduleas the RRC's wellbore query lists them, a well per wellbore and lease
0
producing
1
shut in
0
injection
0
temp. abandoned
72
plugged

Operator of record and permit operator

74 wellbores of record

0
it permitted itself
3
acquired: another operator's permit
71
no permit on file

0 wellbores it permitted

0
run by other operators today
0
live permits, no operator of record yet
0
RRC lists no operator of record

A well's operator of record is the RRC's, and its permit operator is the one on its latest drilling permit; neither fills in for the other. Its wellbores of record are counted as its wells, with its live permits; a well it permitted that another operator runs, or that the RRC lists with no operator at all, is not. Each count opens the wells it counts. Transfers and operator numbers →

Fields

RRC regulatory fields with the most wells of record under this operator. The field opens its page; the count opens this operator's wells in it.

P-5 organization report

As registered with the RRC. About the P-5 →

Registration
Status Delinquent (D)
Last filed Dec 10, 2013
Oil operator
Address
5949 Sherry LN Ste 1050
Dallas, TX 75225
(972) 677-7690
Officers and agents
Looper, Steven Earl · Managing Member
Looper, Robin Moody · Managing Member
Kelly, Joseph Gerard · Managing Member

Latest permits

NEWEST FIRST BY ISSUE DATE · FILED OR ON WELLS IT NOW OPERATES

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
323108Nov 25, 1986Nov 25, 1986Cal-T Oil CompanyHutchinsonLuginbyhl "C" #23,19023384166
237734May 4, 1984May 4, 1984GbiHutchinsonBrown, Carol #23,45023331904
58278Sep 18, 1979Sep 18, 1979Dyne Oil & Gas,inc.HutchinsonLuginbyhl 'B' #83,80023330737

Full permit history →

About this data

Registration from the RRC P-5 organization report, refreshed weekly. Permits from the OGA049M master and daily daf420 files; wells of record from the EWA wellbore schedule; production from PDQ lease reports by the operator that filed them, through the statewide reported-through month; disposal from UIC permits and H-10 reports. Oil includes condensate from gas leases and gas includes casinghead gas from oil leases, as the RRC totals them. Summary figures are rebuilt nightly. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/operators/tx/684631, documented in the API reference.