WELL · 42-485-46414 · DISTRICT 13

Bradley #31T

N

Wichita County  · Vertical

Bradley #31T (API 42-485-46414) is a permitted well in Wichita County filed by R2q Operating LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued August 14, 2025, permitted to 5,000 ft.

Operator of record

R2Q Operating LLC

Iowa Park, TX · P-5 Y, filed Jul 4, 2026 · 38 permits on file · (940) 733-8152

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitR2Q Operating LLCAug 14, 2025
5,000
total depth, ft
1
permits on file
Aug 14, 2025
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

33.873214, -98.845194

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Wichita County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
909812-99DrillR2Q Operating LLCAug 12, 2025Aug 14, 2025Aug 18, 20255,000

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Bradley B42-485-46145

0.8 KM · Texas Energy Operations, LC · Section with this well →

Bluff Creek Sand—
Gunsight—
Gunsight—
Cisco—
Canyon—
Vogstberger—
Thomas Sand—
Tannehill—

10 TOPS · FIRST 8

Bradley B42-485-46056

1.1 KM · Texas Energy Operations, LC · Section with this well →

Tannehill94569
Cisco1,250-236
Thomas Sand1,590-576
Gunsight1,815-801
Gunsight1,830-816
Canyon2,455-1,441
Bluff Creek Sand2,660-1,646
KMA3,675-2,661

10 TOPS · FIRST 8

Bradley Ranch42-485-46086

1.5 KM · Texas Energy Operations, LC · Section with this well →

Cisco1,00087
Gunsight1,980-893
Gunsight2,000-913
Canyon2,410-1,323
KMA3,886-2,799
Strawn—
Tannehill—
Thomas Sand—

10 TOPS · FIRST 8

Nance /Deep/42-485-46122

1.6 KM · Slant Operating, LLC · Section with this well →

Gunsight1,809-798
Gunsight1,824-813
KMA3,711-2,700
Vogstberger—
Bluff Creek Sand—
Thomas Sand—
Tannehill—
Cisco—

10 TOPS · FIRST 8

Munger42-485-46181

2.1 KM · White Knight Production LLC · Section with this well →

Canyon1,776-763
KMA3,646-2,633
Tannehill—
Strawn—
Gunsight—
Gunsight—
Cisco—
Bluff Creek Sand—

10 TOPS · FIRST 8

Munger42-485-46180

2.4 KM · White Knight Production LLC · Section with this well →

Gunsight1,769-758
KMA3,906-2,895
Vogstberger—
Bluff Creek Sand—
Caddo—
Canyon—
Cisco—
Gunsight—

11 TOPS · FIRST 8

Graham42-485-46164

2.7 KM · White Knight Production LLC · Section with this well →

Gunsight1,757
Canyon3,240
KMA3,641
Tannehill—
Gunsight—
Bluff Creek Sand—
Thomas Sand—
Strawn—

10 TOPS · FIRST 8

W. L. Hodges42-485-46330

2.9 KM · LMH Energy · Section with this well →

Thomas Sand1,500-476
Gunsight1,750-726
Canyon2,516-1,492
Vogstberger—
Bluff Creek Sand—
Cisco—
Gunsight—
KMA—

10 TOPS · FIRST 8

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