TEXAS · WELLS · WICHITA COUNTY · BRADLEY LEASE · API 42-485-44366 · DISTRICT 7C

Bradley #1T

Shut in

Wichita County · K-M-A field · Shut In  · Vertical

Fields on the latest permit · any of 2
Hammon (Ellenburger) · K-M-A
Not one formation; the well must be completed in one of them, and no target formation is stated.

Bradley #1T (API 42-485-44366) is a well in Wichita County operated by R2q Operating LLC, completed October 11, 2012 and listed as shut in on the RRC schedule, shut in April 1, 2021.

The RRC has issued one drilling permit, issued March 18, 2008, permitted to 4,250 ft.

It was permitted by Texas Energy Operations, LC and has since transferred to R2q Operating LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Gunsight, K M A Lime, K-M-A Lime, Kma Lime.

Its lease has reported 120K barrels of oil since July 2008, last reporting volume in February 2026. The lease carries 10 wells, so these are lease totals, not this well alone.

Operator of record

R2Q Operating LLC

Permitted by Texas Energy Operations, LC; the EWA schedule now lists a different operator.

Based in
Iowa Park, TX
P-5 status
Active – Extension (X)
P-5 last filed
Sep 12, 2025
Permits on file
38
Phone
(940) 228-1500

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleR2Q Operating LLC
Production reportsR2Q Operating LLCthrough Feb 2026
Latest permitTexas Energy Operations, LCMar 18, 2008

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

4,250
total depth, ft
1
permits on file
Mar 18, 2008
last permit issued
Oct 11, 2012
completed
120K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2008 THROUGH Feb 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 11, 2012
Shut in
Apr 1, 2021
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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; they carry 10 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bradley O-13-31079K-M-AR2Q Operating LLC10120K0Jul 2008 – Feb 2026

Oil, barrels lease total

Last 12 months 2,694 · prior 12 3,724(-28%)

0200400600202420252026

Chain of custody

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

  1. 1Texas Energy Operations, LCJul 2008 → Dec 2019
  2. 2R2Q Operating LLCJan 2020 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
656852-99DrillTexas Energy Operations, LCMar 6, 2008Mar 18, 2008Mar 27, 20084,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 11, 2012Bradley O-13-31079K-M-AR2Q Operating LLCShut In · shut in Apr 1, 20214,250

Formation tops

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

FormationMD ftSubsea
Gunsight1,800-803
K M A Lime3,680-2,683
K-M-A Lime3,680-2,683
Kma Lime3,680-2,683

Perforations

Perforated and open-hole intervals.

FromToType
3,7023,730Perforated
3,7663,772Perforated
3,8203,890Perforated
4,2504,306Perforated
4,2504,314Perforated
4,2964,306Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6258412.2580 S
5.54,3217.875200 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Mar 7, 2013Nov 1, 2012—
00Dec 15, 2011Sep 9, 2011—
00Nov 4, 2009Jun 1, 2009—
00Nov 20, 2008Jul 30, 2008Yes
00Nov 6, 2008——

Well logs

1 log loaded from the RRC's log index, the latest received May 6, 2011. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Gunsight, Kma Lime, K M A Lime, K-M-A LimeTIFF80 to 3,839May 6, 2011run Apr 1, 20081.82

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

176K
bbl, last 12 reported months
176K
bbl, all reported
Apr 2012
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000102961H-1 InjectionCanceled Aug 7, 20133,0002,1204,250–4,314

MONTHLY INJECTED, BBL · H-10 · LAST 12 REPORTED MONTHS

Last 12 months 175,898

020K40K60K2012

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