WELL · 42-083-34482 · DISTRICT 7

J.R. Ranch #2

Y

Coleman County · Traci (Morris) field · Producing  · Vertical

J.R. Ranch #2 (API 42-083-34482) is a well in Coleman County operated by Quail Well Service Inc., completed July 4, 1985 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued June 17, 1985, permitted to 2,700 ft.

It was permitted by Fargo Exploration CO. and has since transferred to Quail Well Service Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Palo Pinto, Dog Bend Ls., Morris Sd.

Its lease has reported 19.6K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Quail Well Service Inc.

Permitted by Fargo Exploration Co.; the EWA schedule now lists a different operator.

Abilene, TX · P-5 Y, filed Jul 4, 2026 · 92 permits on file · (325) 201-7560

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleQuail Well Service Inc.
Production reportsQuail Well Service, Inc.through Apr 2026
Latest permitFargo Exploration Co.Jun 17, 1985

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

2,700
total depth, ft
1
permits on file
Jun 17, 1985
last permit issued
Jul 4, 1985
completed
19.6K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 4, 1985
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
J.R. Ranch O-8-22693Traci (Morris)Quail Well Service, Inc.119.6K21Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 492 · prior 12 244(+102%)

0100200300202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Fargo Exploration Co.Jan 1993 → Dec 1995
  2. 2Quail Well Service, Inc.Jan 1996 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
277942-99DrillFargo Exploration Co.Jun 17, 1985Jun 17, 1985Jun 20, 19852,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-22693————

Formation tops

As filed on W-2/G-1. Subsea from 1,845 ft elevation.Download CSV →

FormationMD ftSubsea
Palo PintoPALO PINTO LS.2,030-185
Dog Bend Ls.2,452-607
Morris SD2,505-660

Perforations

Perforated and open-hole intervals.

FromToType
2,5082,513Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62512611100 S
4.52,5537.875125 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 30, 1985Jul 8, 1985—
00Jul 23, 1985——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/08334482, documented in the API reference.