WELL · 42-023-31666 · DISTRICT 9

Upshur 83 #1

Plugged

Baylor County · Baylor County Regular field  · Vertical

Upshur 83 #1 (API 42-023-31666) 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 February 26, 2014, permitted to 4,950 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, Palo Pinto, Strawn, Cisco.

Its lease has reported 10.1K barrels of oil and 8.89K mcf of gas since April 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.Feb 26, 2014

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

4,950
total depth, ft
1
permits on file
Feb 26, 2014
last permit issued
Apr 4, 2014
completed
10.1K
cumulative oil, bbl
8.89K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2014 THROUGH Apr 2022

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 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 83 O-13-32951Baylor County RegularMash Oilfield Services, LP110.1K8.89KApr 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.Apr 2014 → Feb 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
779893-99DrillClark, John M., Inc.Feb 14, 2014Feb 26, 2014Mar 11, 20144,950

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-32951————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON REEF2,280-952
Palo Pinto2,280-952
Strawn3,618-2,290
Cisco——
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE ZON——
GunsightGUNSIGHT SAND——
Home Creek——
Saddle Creek——
TannehillTANNEHILL SAND——
Thomas Sand——

Perforations

Perforated and open-hole intervals.

FromToType
4,8004,815Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62521112.25130 S
5.54,8997.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
00Aug 26, 2014Aug 11, 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/02331666, documented in the API reference.