WELL · 42-023-31645 · DISTRICT 9

Upshur 60 #1

Plugged

Baylor County · Baylor County Regular field  · Vertical

Upshur 60 #1 (API 42-023-31645) 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 August 20, 2012, permitted to 5,400 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 3 formation tops, including Coleman Junction, Caddo, Mississippian.

Its lease has reported 36.4K barrels of oil and 11.5K mcf of gas since February 2013, last reporting in April 2022. The lease carries 3 wells, so these are lease totals, not this well alone.

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.Aug 20, 2012

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

5,400
total depth, ft
1
permits on file
Aug 20, 2012
last permit issued
Feb 1, 2013
completed
36.4K
cumulative oil, bbl
11.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2013 THROUGH Apr 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 1, 2013
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; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Upshur 60 O-13-32729Baylor County RegularMash Oilfield Services, LP336.4K11.5KFeb 2013 – 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.Feb 2013 → Feb 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
746273-99DrillClark, John M., Inc.Aug 10, 2012Aug 20, 2012Nov 14, 20125,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-32729————

Formation tops

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

FormationMD ftSubsea
Coleman JunctionBASE COLEMAN JUNCTION538707
CaddoTOP CADDO LIME4,714-3,469
MississippianTOP MISSISSIPPIAN LIME5,214-3,969

Perforations

Perforated and open-hole intervals.

FromToType
4,7144,722Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521112.25165 S
5.55,2487.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
00Dec 17, 2013Aug 6, 2013Yes

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