WELL · 42-237-39404 · DISTRICT 9

Ruby #1

Plugged

Jack County · JMG Mag (Miss) field  · Vertical

Ruby #1 (API 42-237-39404) is a plugged well in Jack County, plugged June 9, 2023, last operated by Best Petroleum Explorations Inc..

The RRC has issued one drilling permit (amended once), issued March 29, 2011, permitted to 6,000 ft.

Completion filings report 5 formation tops, including Strawn, Caddo, Congl, Congl..

Its 2 leases have reported 35.3K barrels of oil and 1.06M mcf of gas since June 2011, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Best Petroleum Explorations Inc.

Jacksboro, TX · P-5 Y, filed Oct 4, 2025 · 251 permits on file · (940) 229-9039

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBest Petroleum Explorations Inc.
Production reportsBest Petroleum Explorations,inc.through Dec 2023
Latest permitBest Petroleum Explorations,inc.Mar 29, 2011
6,000
total depth, ft
2
permits on file
Mar 29, 2011
last permit issued
Jun 8, 2011
completed
35.3K
cumulative oil, bbl
1.06M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 8, 2011
Shut in
—
Plugged
Jun 9, 2023

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 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Ruby O-13-31947JMG Mag (Miss)Best Petroleum Explorations,inc.235.3K550KJun 2011 – Jul 2026
Ruby G-13-267646JMG Mag (Miss)Best Petroleum Explorations,inc.10511KDec 2012 – Jun 2023

Gas, mcf lease total

Last 12 months 0 · prior 12 0

0100200202420252026

Oil, barrels lease total

Last 12 months 0 · prior 12 0

024202420252026

Chain of custody

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

  1. 1Best Petroleum Explorations,inc.Jun 2011 → Dec 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
712816-98DrillBest Petroleum Explorations,inc.Jul 8, 2011Mar 29, 2011May 17, 20116,000
712816-99DrillBest Petroleum Explorations,inc.Mar 24, 2011Mar 29, 2011May 16, 20116,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-267646————
—— O-13-31947————

Formation tops

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

FormationMD ftSubsea
Strawn3,400-2,199
CaddoCADDO CONGL4,570-3,369
CaddoCADDO CONGL.4,570-3,369
Congl4,750-3,549
Congl.4,750-3,549
Marble Falls4,800-3,599

Perforations

Perforated and open-hole intervals.

FromToType
4,7505,300Perforated
4,9905,210Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62533012.25200 S
4.55,3067.875400 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
00May 13, 2013Jan 7, 2013—
00Jan 31, 2012Jul 15, 2011Yes

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