WELL · 42-503-39630 · DISTRICT 9

Marshall #2

Plugged

Young County · Taylor (Strawn) field  · Vertical

Marshall #2 (API 42-503-39630) is a plugged well in Young County, plugged July 24, 2023, last operated by Oakmont Oil And Gas.

The RRC has issued one drilling permit, issued September 23, 1987, permitted to 4,600 ft.

It was permitted by Three P Operating Company and has since transferred to Oakmont Oil And Gas on the wellbore schedule.

Completion filings report 2 formation tops, including Buttrum Sand, Taylor.

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

Operator of record

Oakmont Oil and Gas

Permitted by Three P Operating Company; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Jan 5, 2026 · (942) 229-1228

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOakmont Oil and Gas
Production reportsOakmont Oil and Gasthrough Apr 2026
Latest permitThree P Operating CompanySep 23, 1987

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

4,600
total depth, ft
1
permits on file
Sep 23, 1987
last permit issued
Dec 5, 1987
completed
152K
cumulative oil, bbl
9
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 5, 1987
Shut in
—
Plugged
Jul 24, 2023

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 6 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Marshall O-13-26409Taylor (Strawn)Oakmont Oil and Gas6152K9Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 2,301 · prior 12 1,220(+89%)

0200400600202420252026

Chain of custody

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

  1. 1Three P Operating CompanyJan 1993 → Nov 2007
  2. 2Three P Operating Co.,gp, L.L.C.Dec 2007 → Oct 2024
  3. 3Oakmont Oil and GasNov 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
336258-99DrillThree P Operating CompanySep 21, 1987Sep 23, 1987—4,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-26409————

Formation tops

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

FormationMD ftSubsea
Buttrum Sand2,810-1,530
TaylorTAYLOR (STRAWN)3,465-2,185

Perforations

Perforated and open-hole intervals.

FromToType
3,4693,472Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62545612.25260 S
4.53,5957.875100 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 29, 1987Dec 15, 1987Yes
00Dec 22, 1987——

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