WELL · 42-337-33464 · DISTRICT 9

Bouldin #53

Y

Montague County · Montague County Regular field · Producing  · Vertical

Bouldin #53 (API 42-337-33464) is a well in Montague County operated by Hadley Oil Company LLC, completed May 14, 2002 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 10, 2002, permitted to 1,999 ft.

It was permitted by Hadley Oil and has since transferred to Hadley Oil Company LLC on the wellbore schedule.

Completion filings report 2 formation tops, including 800 Sand, 1500 Sand.

Its lease has reported 81.2K barrels of oil and 22 mcf of gas since January 1993, last reporting in July 2026. The lease carries 35 wells, so these are lease totals, not this well alone.

Operator of record

Hadley Oil Company LLC

Permitted by Hadley Oil; the EWA schedule now lists a different operator.

Nocona, TX · P-5 Y, filed Nov 4, 2025 · 2 permits on file · (940) 825-6218

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHadley Oil Company LLC
Production reportsHadley Oil Company, LLCthrough Apr 2026
Latest permitHadley OilMay 10, 2002

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

1,999
total depth, ft
1
permits on file
May 10, 2002
last permit issued
May 14, 2002
completed
81.2K
cumulative oil, bbl
22
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 14, 2002
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; they carry 35 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bouldin O-13-4187Montague County RegularHadley Oil Company, LLC3581.2K22Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 1,043 · prior 12 1,081(-4%)

050100150202420252026

Chain of custody

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

  1. 1Patrick, George & Patrick, RogerJan 1993 → Jul 1999
  2. 2Hadley OilAug 1999 → Jan 2014
  3. 3Hadley Oil Company, LLCFeb 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
519891-99DrillHadley OilMay 10, 2002May 10, 2002May 14, 20021,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-4187————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
800 Sand868
1500 Sand1,536

Perforations

Perforated and open-hole intervals.

FromToType
1,5361,540Perforated
1,5401,546Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
5.51,5887.875360 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 31, 2002Jul 2, 2002Yes
00Jul 9, 2002——

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