OPERATORS · RRC 270552  · P-5 STATUS Y

Fisher Productions

Fisher Productions has filed no drilling permits in the past 12 months; its most recent permit was issued August 26, 1988.

The RRC wellbore file lists 10 wells under its operatorship.

4 drilling permits have been issued to this operator number since 1982; its P-5 organization report was last filed May 3, 2002.

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

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

Where

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

County12 moAll timeWellsLast
Brown county →—410Aug 26, 1988

All 4 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
Marble Falls20
Caddo20
Duffer10

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
2.14K
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

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

How it got them

0
permitted itself
6
acquired from others
2
permitted, now run by others

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

RRC UIC permits · H-10 reported volumes

Disposal and injection

0
active UIC permits of 4
0
permitted bbl/day, active
0
bbl injected, last 12 reported months
Jun 2025
reported through

By county

Brown0 active0 bbl/d

Permitted volume is a ceiling, not throughput. How to read it →

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
Drill002
Recompletion002

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
Brown County Regular12406001100

P-5 organization report

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

Registration
Status code Y
Last filed May 3, 2002
Address
5806 Secrest Dr.
Austin, TX 78759
Officers and agents
Fisher, Jerry · Texas Resident Agent
Fisher, Stanley Walter · Partner
Fisher, Walter D. · Partner

Latest permits

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

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
350429Aug 26, 1988Aug 26, 1988Fisher ProductionsBrownBriggs #32,80004935059
337251Oct 13, 1987Oct 13, 1987Fisher ProductionsBrownGlasscock, Melvin #22,70404932817
337251Oct 13, 1987Oct 13, 1987Fisher ProductionsBrownGlasscock, Melvin #22,70404932817
247808Aug 8, 1984Aug 8, 1984Hui, IncBrownBrown #1020004934104
247799Aug 8, 1984Aug 8, 1984Hui, IncBrownBrown #1120004934103
246213Jul 24, 1984Jul 24, 1984Hui, IncBrownBrown #820004934081
242912Jun 25, 1984Jun 25, 1984Hui, IncBrownBrown #720004934051
242901Jun 25, 1984Jun 25, 1984Hui, IncBrownBrown #620004934049
201979Jul 19, 1983Jul 19, 1983Haynes Production Company, Inc.BrownFisher, Walter A #B13,20004933636
175384Oct 26, 1982Oct 26, 1982Fisher ProductionsBrownDority #12,80004933329

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/270552, documented in the API reference.