OPERATORS · RRC 128546  · P-5 STATUS Y

Calyx Expl & Prod. Corp

Calyx Expl & Prod. Corp has filed no drilling permits in the past 12 months; its most recent permit was issued August 2, 1989.

The RRC wellbore file lists 2 wells under its operatorship.

5 drilling permits have been issued to this operator number since 1987; its P-5 organization report was last filed September 2, 2016.

0
permits, last 12 months
—
vs prior 12 months (0)
0
counties, 12 months
0
producing wells, of 2 of record
2
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.

0%
spud rate · 0 of 5 mature permits
—
median days permit to spud
0
spuds, last 180 days
0%
cancelled · 0 permits
5
expired undrilled
3
permits a year over 2 active years

Where

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

County12 moAll timeWellsLast
Cass county →—42Nov 18, 1988
Nacogdoches county →—10Aug 2, 1989

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
Rodessa20
Pettit10
Travis Peak10
Massive Anhydrite (marker)10

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

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

How it got them

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

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
Rambo North (Rodessa 6100)7439940010
Wildcat1200110

P-5 organization report

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

Registration
Status code Y
Last filed Sep 2, 2016
Oil operator
Address
5445 la Sierra, Suite 204
Dallas, TX 75231
Officers and agents
Pretus, Robert H. · Texas Resident Agent
Washington, Timothy · President
Pretus, Robert H. · Vice President/Secretary/Directo
Skalnik, Petr · Manager

Latest permits

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

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
362297Aug 2, 1989Aug 2, 1989Calyx Exploration & Prod. Corp.NacogdochesHill, R.C. #13,70034731570
353449Nov 18, 1988Nov 18, 1988Calyx Exploration & Prod. Corp.CassPenn #16,70006730602
348542Jul 8, 1988Jul 8, 1988Calyx Exploration & Prod. Corp.CassManville #26,30006730588
348542Jul 8, 1988Jul 8, 1988Calyx Exploration & Prod. Corp.CassManville #26,44006730588
340424Dec 22, 1987Dec 22, 1987Calyx Exploration & Prod. Corp.CassManville #17,00006730570

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