WELL · 42-267-30396 · DISTRICT 7

Mudge #4

Y

Kimble County · Shajumar (Canyon) field · Temp Abandoned  · Vertical

Mudge #4 (API 42-267-30396) is a well in Kimble County operated by Concho Oilfield Serv & Oper CO., completed October 25, 2003 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued September 4, 2003, permitted to 2,000 ft.

It was permitted by Britnic Oil & Gas, Inc. and has since transferred to Concho Oilfield Serv & Oper CO. on the wellbore schedule.

Completion filings report 2 formation tops, including Palo Pinto, Canyon.

No lease production has been reported under this well’s leases.

Operator of record

Concho Oilfield Serv & Oper Co.

Permitted by Britnic Oil & Gas, Inc.; the EWA schedule now lists a different operator.

Eden, TX · P-5 Y, filed Feb 4, 2026 · 11 permits on file · (325) 456-0685

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleConcho Oilfield Serv & Oper Co.
Production reportsMextex Operating Companythrough Aug 2018
Latest permitBritnic Oil & Gas, Inc.Sep 4, 2003

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

2,000
total depth, ft
2
permits on file
Sep 4, 2003
last permit issued
Oct 25, 2003
completed
0
cumulative oil, bbl
249K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 25, 2003
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Mudge G-9-199589Shajumar (Canyon)Concho Oilfield Serv & Oper Co.10249KOct 2003 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Britnic Oil & Gas, Inc.Dec 2003 → Jun 2004
  2. 2O.G.P. Operating, Inc.Jul 2004 → Jun 2006
  3. 3Mextex Operating CompanyJul 2006 → Aug 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
536060-98DrillBritnic Oil & Gas, Inc.Oct 9, 2003Sep 4, 2003Oct 14, 20032,000
536060-99DrillBritnic Oil & Gas, Inc.Sep 4, 2003Sep 4, 2003—2,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-199589————

Formation tops

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

FormationMD ftSubsea
Palo Pinto1,260602
Canyon1,464398

Perforations

Perforated and open-hole intervals.

FromToType
1,4681,502Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
7.6253259.875145 S
4.51,5706.75160 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
00Apr 5, 2004Feb 12, 2004Yes
00Mar 8, 2004——

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