WELL · 42-023-31663 · DISTRICT 9

Upshur 72 #1

Plugged

Baylor County · Baylor County Regular field  · Vertical

Upshur 72 #1 (API 42-023-31663) is a plugged well in Baylor County, plugged April 14, 2022, last operated by Mash Oilfield Services LP.

The RRC has issued one drilling permit, issued January 9, 2014, permitted to 5,500 ft.

It was permitted by Clark, John M., Inc. and has since transferred to Mash Oilfield Services LP on the wellbore schedule.

Completion filings report 10 formation tops, including Canyon, Cisco, Coleman Junction, Conglomerate.

Its lease has reported 7.87K barrels of oil and 8.54K mcf of gas since March 2014, last reporting in April 2022.

Operator of record

Mash Oilfield Services LP

Permitted by Clark, John M., Inc.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed May 4, 2026 · 1 permits on file · (940) 456-1223

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMash Oilfield Services LP
Production reportsClark, John M., Inc.through Feb 2021
Latest permitClark, John M., Inc.Jan 9, 2014

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

5,500
total depth, ft
1
permits on file
Jan 9, 2014
last permit issued
Mar 4, 2014
completed
7.87K
cumulative oil, bbl
8.54K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2014 THROUGH Apr 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 4, 2014
Shut in
—
Plugged
Apr 14, 2022

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
Upshur 72 O-13-32814Baylor County RegularMash Oilfield Services, LP17.87K8.54KMar 2014 – Apr 2022

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. 1Clark, John M., Inc.Mar 2014 → Feb 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
776952-99DrillClark, John M., Inc.Jan 9, 2014Jan 9, 2014Jan 17, 20145,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-32814————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON REEF——
Cisco——
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON——
Conglomerate——
GunsightGUNSIGHT SAND——
Home Creek——
Mississippian——
Saddle Creek——
TannehillTANNEHILL SAND——
Thomas Sand——

Perforations

Perforated and open-hole intervals.

FromToType
4,7624,778Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521112.25130 S
5.55,1577.875175 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 14, 2014Mar 24, 2014Yes

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