OPERATORS · RRC 427890  · P-5 STATUS Y

J-R Oil Inc.

J-R Oil Inc. has filed no drilling permits in the past 12 months.

The RRC wellbore file lists 104 wells under its operatorship.

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

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

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

How it got them

0
permitted itself
18
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 10
0
permitted bbl/day, active
0
bbl injected, last 12 reported months
Jun 2025
reported through

By county

Kent0 active0 bbl/d
Taylor0 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.

P-5 organization report

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

Registration
Status code Y
Last filed Aug 6, 2004
Address
17018 Knots Lndg
Dallas, TX 75248
Officers and agents
Stockman, R. J. · Ceo/Secretary
Ray, James L. · President

Latest permits

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

PermitSeenIssuedOperatorCountyLease / wellDepthAPI
439558Sep 5, 1995Sep 5, 1995Myd, Inc.KentNewman #37,00026300320
425429Jun 29, 1994Jun 29, 1994Myd, Inc.KentWallace #17,00026300700
422200May 6, 1994May 6, 1994Petroleum Property Mgmt, Inc (A)KentReed "A" #46,75026300642
422200May 6, 1994May 6, 1994Myd, Inc.KentReed "A" #46,74126300642
422801Apr 7, 1994Apr 7, 1994Rocker a Operating CompanyKentEisner, J. - Maben, E. #17,50026300150
422801Apr 7, 1994Apr 7, 1994Dynamic Production, Inc.KentMaben #2D7,18226300150
415638Oct 15, 1993Oct 15, 1993Petroleum Property Mgmt, Inc (A)KentReed "A" #26,75026300641
403989Oct 21, 1992Oct 21, 1992H & S Production, Inc.KentReed #26,72526300756
375914Jul 31, 1990Jul 31, 1990McDonald Production, Inc.FisherHawkins #35,46115110435
349653Nov 18, 1988Nov 18, 1988Rozeman, Abe M.BrownKoch #13,00004930698
348465Jul 13, 1988Jul 13, 1988Sabre Development & ExplorationTaylorBlackwell #14,99044133322
348465Jul 13, 1988Jul 13, 1988Sabre Development & ExplorationTaylorBlackwell #14,99044133322
294668Jan 7, 1986Jan 7, 1986Royalty Investments CompanyFisherWithers #16,89115100292
294668Jan 7, 1986Jan 7, 1986Royalty Investments CompanyFisherWithers #16,89115100292
273821Apr 30, 1985Apr 30, 1985Newman Brothers Drilling CompanyKentSMS Canyon Sand Unit #1826,70026300045

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