OPERATORS · RRC 28736  · P-5 STATUS Y

Arc Energy Inc.

Arc Energy Inc. has filed no drilling permits in the past 12 months.

The RRC wellbore file lists 28 wells under its operatorship.

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

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

Where

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

CountyWellsProducing
Navarro county →20—
Denton county →8—

All 0 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
2.21K
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

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

How it got them

0
permitted itself
13
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 →

RRC UIC permits · H-10 reported volumes

Disposal and injection

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

By county

Denton0 active0 bbl/d
Navarro0 active0 bbl/d

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

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
Corsicana (Shallow)20823500200
Bolivar1027500180

P-5 organization report

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

Registration
Status code Y
Last filed Nov 6, 2020
Address
P O Box 270784
Dallas, TX 75227
(214) 335-2220
Officers and agents
Ford, Taylor · Texas Resident Agent
Ford, Floyd Taylor · President/Secretary

Latest permits

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

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
121507Jun 17, 1981Jun 17, 1981Explorer Energy Corp.NavarroIngham, J. D. #5A1,40034931771
120304Jun 9, 1981Jun 9, 1981Explorer Energy Corp.NavarroIngham, J.D. #3A1,40034931747
119398May 8, 1981May 8, 1981Explorer Energy Corp.NavarroIngham, J.D. #8A1,50034931736
120302Apr 30, 1981Apr 30, 1981Explorer Energy Corp.NavarroIngham, J.D. #1A1,40034931746
76382Mar 27, 1980Mar 27, 1980Pyron InvestmentsNavarroIngham, J. D. #41,42134931186
76378Mar 27, 1980Mar 27, 1980Pyron InvestmentsNavarroIngham, J. D. #61,37334931184
76380Mar 27, 1980Mar 27, 1980Gordon, Willard D.NavarroIngham, J. D. #51,50034931185
71745Feb 5, 1980Feb 5, 1980Walters, G. C., Jr.NavarroIngham, J. D. #21,30034931139
71742Feb 5, 1980Feb 5, 1980Walters, G. C., Jr.NavarroIngham, J. D. #11,30034931138
71740Feb 5, 1980Feb 5, 1980Walters, G. C., Jr.NavarroIngham, J. D. #31,30034931137
49320May 25, 1979May 25, 1979Smith, J. T. Co.NavarroHighnote #61,00034930884
47213Apr 25, 1979Apr 25, 1979Smith, J. T. Co.NavarroHighnote #31,60034930875
47212Apr 25, 1979Apr 25, 1979Smith, J. T. Co.NavarroHighnote #41,60034930874

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