OPERATORS · RRC 432078  · P-5 STATUS Y

Jerco Enterprises, Inc

Jerco Enterprises, Inc has filed no drilling permits in the past 12 months; its most recent permit was issued September 28, 1981.

The RRC wellbore file lists 1 well under its operatorship.

5 drilling permits have been issued to this operator number since 1977; its P-5 organization report was last filed April 15, 1991.

0
permits, last 12 months
—
vs prior 12 months (0)
0
counties, 12 months
0
producing wells, of 1 of record
0
leases it reports
—
horizontal, 12 months

WINDOWS ON THE RRC ISSUE DATE · COMPUTED OCT 29, 2026

From permit to spud

FROM THE DATES ON ITS W-1 PERMITS · ALL TIME

A permit is a plan, not a well. These figures count only permits old enough to have spudded, six months and more, and read the spud, cancel, and expiry dates the RRC records on each one.

20%
spud rate · 1 of 5 mature permits
94
median days permit to spud · middle half 94–94
0
spuds, last 180 days
20%
cancelled · 1 permits
3
expired undrilled
1
permits a year over 5 active years

Where

Counties by permits in the last 12 months, with all-time permits and current wells of record there.

County12 moAll timeWellsLast
Zavala county →—50Sep 28, 1981

All 5 permits, searchable → · Leases it reports → · On the map →

Formations in its completed wells

Tops reported on completion filings for wells it operates. 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. How production is reported →

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

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

Beyond the permit record

RRC wellbore file

Wells of record

1
on the schedule
0
producing
0
shut in
0
injection
0
temp. abandoned
1
plugged

How it got them

0
permitted itself
1
acquired from others
0
permitted, now run by others

Acquired means the well's permit names a different operator than the schedule does today. Transfers and operator numbers →

Permit types

Last 12 months against the prior 12, and all time. A type opens the permit history filtered to it. What the types mean →

Type12 moPrior 12All time
Drill005

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.

FieldWellsProducing
Cooke(wilcox 5350)2033692510

P-5 organization report

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

Registration
Status code Y
Last filed Apr 15, 1991
Address
15417 House Road
Hockley, TX 77447
Officers and agents
House, Jerry L. · President
House, Brenda J. · Secretary

Latest permits

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

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
134643Sep 28, 1981Sep 28, 1981Jerco Enterprises, Inc.ZavalaJ. L. H. Land Investments Corp. #3-A2,00050731581
99789Nov 19, 1980Nov 19, 1980Jerco Enterprises, Inc.ZavalaJ.L.H. Land Investments Corp. #1A1,70050731420
73482Feb 25, 1980Feb 25, 1980Jerco Enterprises, Inc.ZavalaJ.L.H. Land Investments Corp. #3A2,20050731321
33146Sep 21, 1978Sep 21, 1978Mormac Oil & Gas Co & Null,w.m.LA SalleGausemeier, Lena "A" #15,50028330638
5982Aug 23, 1977Aug 23, 1977Jerco Enterprises, Inc.ZavalaJ.L.H. Land Investments Corp. #43,50050730896
809Jun 16, 1977Jun 16, 1977Jerco Enterprises, Inc.ZavalaJ. L. H. Land Investments Corp #31,30050730870

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 at the last vintage; disposal from UIC permits and H-10 reports. Summary figures are rebuilt nightly.

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