TEXAS · WELLS · FREESTONE COUNTY · YORK, B. P. LEASE · API 42-161-31780 · DISTRICT 05

York B. P. #4

Plugged

Freestone County · Teague (CV-Bossier Cons.) field  · Vertical

York B. P. #4 (API 42-161-31780) is a plugged well in Freestone County, plugged November 28, 2022, last operated by Valence Operating Company.

The RRC has issued one drilling permit, issued June 8, 2000, permitted to 12,700 ft.

Completion filings report 6 formation tops, including Budda, BMA, Pettit, Travis Peak.

Its lease has reported 163 barrels of oil and 497K mcf of gas since October 2000, with no volume in the three years through April 2026.

Operator of record

Valence Operating Company

Based in
Kingwood, TX
P-5 status
Active (A)
P-5 last filed
Jun 4, 2026
Permits on file
990
Phone
(281) 359-3659

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleValence Operating Company
Production reportsValence Operating Companythrough Jul 2011
Latest permitValence Operating CompanyJun 8, 2000
12,700
total depth, ft
1
permits on file
Jun 8, 2000
last permit issued
Oct 20, 2000
completed
163
cumulative oil, bbl
497K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2000 THROUGH Jul 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 20, 2000
Shut in
—
Plugged
Nov 28, 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
York, B. P. G-5-180068Teague (CV-Bossier Cons.)Valence Operating Company1163497KOct 2000 – Jul 2011

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. 1Valence Operating CompanyOct 2000 → Jul 2011

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
495299-99DrillValence Operating CompanyMay 19, 2000Jun 8, 2000Aug 20, 200012,700

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 20, 2000York B. P. G-5-180068Teague (CV-Bossier Cons.)Valence Operating CompanyPlugged—

Formation tops

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

FormationMD ftSubsea
Budda5,070-4,642
BMA7,790-7,362
Pettit8,535-8,107
Travis Peak8,756-8,328
Cotton ValleyCOTTON VALLEY SD10,600-10,172
Bossier12,170-11,742

Perforations

Perforated and open-hole intervals.

FromToType
12,15012,160Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6255,22812.25465 S
4.512,4217.8751,745 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Mar 24, 2001Jan 16, 2001—
00Feb 13, 2001Dec 7, 2000Yes
00Jan 2, 2001——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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