WELL · 42-211-35605 · DISTRICT 10

Fields #1

Y

Hemphill County · Parsell SE. (Douglas) field · Producing  · Vertical

Fields #1 (API 42-211-35605) is a well in Hemphill County operated by Upland Resources LLC, completed March 14, 2018 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 24, 2018, permitted to 7,000 ft.

Completion filings report 9 formation tops, including Brown Dolomite, Douglas, Brownsville, Cleveland.

Its lease has reported 31.3K barrels of oil and 45.6K mcf of gas since March 2018, last reporting in July 2026.

Operator of record

Upland Resources LLC

Canadian, TX · P-5 Y, filed Oct 4, 2025 · 42 permits on file · (806) 323-3061

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUpland Resources LLC
Production reportsUpland Resources LLCthrough Apr 2026
Latest permitUpland Resources LLCJan 24, 2018
7,000
total depth, ft
1
permits on file
Jan 24, 2018
last permit issued
Mar 14, 2018
completed
31.3K
cumulative oil, bbl
45.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2018 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 14, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

35.955681, -100.536334

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Hemphill County.

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
Fields O-14-9638Parsell, SE. (Douglas)Upland Resources LLC131.3K45.6KMar 2018 – Jul 2026

Oil, barrels lease total

Last 12 months 2,122 · prior 12 2,716(-22%)

0200400202420252026

Gas, mcf lease total

Last 12 months 2,660 · prior 12 5,169(-49%)

05001K202420252026

Chain of custody

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

  1. 1Upland Resources LLCMay 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
835182-99DrillUpland Resources LLCJan 15, 2018Jan 24, 2018Mar 4, 20187,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-14-9638————

Formation tops

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

FormationMD ftSubsea
Brown DolomiteBROWN DOLOMITE - PROD, PRESSURED4,000-1,621
Douglas6,360-3,981
Brownsville——
Cleveland——
Kansas CityKANSAS CITY (HOGSHOOTER)——
OswegoOSWEGO UPPER——
PennsylvanianPENNSYLVANIAN (MARMATON)——
PennsylvanianPENNSYLVANIAN SAND——
Tonkawa——
Topeka——

Perforations

Perforated and open-hole intervals.

FromToType
6,4566,460Perforated
6,4686,470Perforated
6,4786,484Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,76812.25830 S
5.56,8958.75670 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
00Nov 14, 2018Aug 7, 2018Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Parsell-Payne 161/162 A42-393-32761

6.3 KM · Mewbourne Oil Company · Section with this well →

Wolfcamp3,488-1,089
Brown Dolomite3,488-1,089
Douglas6,190-3,791
Tonkawa6,486-4,087
Lecompton (Douglas) - H2S Corros—
Council Grove—
Moore County Lime—
Toronto—

10 TOPS · FIRST 8

Waterfield 'A'42-393-32180

6.9 KM · Unit Petroleum Company · Section with this well →

Brown Dolomite4,119-1,316
Douglas6,930-4,127
Kansas City8,145-5,342
Marmaton9,120-6,317
Granite Wash9,535-6,732
Novi Lime10,675-7,872
13 Finger10,755-7,952

Hill, Ben42-393-31548

7.4 KM · Winright Resources Operating,llc · Section with this well →

Douglas6,270-3,731
Tonkawa6,975-4,436
Atoka9,500-6,961
Morrow9,802-7,263
Morrow9,802-7,263
Morrow9,900-7,361
Chester11,402-8,863

Mahler -A-42-393-30882

7.8 KM · Texas Oil & Gas Corp. · Section with this well →

Granite Wash9,500-6,691
Morrow10,800-7,991
Morrow12,100-9,291

Lorene 14442-393-32744

7.9 KM · Mewbourne Oil Company · Section with this well →

Wolfcamp3,576-941
Brown Dolomite3,576-941
Douglas6,312-3,677
Lecompton (Douglas) - H2S Corros6,312-3,677
Tonkawa6,994-4,359
Albany Dolomite - H2S Corrosive—
Toronto—
Quinduno Brown Dolomite - H2S Co—

10 TOPS · FIRST 8

Vollmert "C"42-211-34298

9.5 KM · Unit Petroleum Company · Section with this well →

Douglas6,917-4,241
Heebner6,917-4,241
Douglas6,917-4,241
Granite Wash9,738-7,062
Novi11,010-8,334

Pioneer 3142-393-32731

9.6 KM · Mewbourne Oil Company · Section with this well →

Brown Dolomite3,697-979
Douglas6,340-3,622
Tonkawa7,061-4,343
Lecompton (Douglas) - H2S Corros—
Council Grove—
Albany Dolomite - H2S Corrosive—
Toronto—
Wolfcamp—

10 TOPS · FIRST 8

Isaacs C42-211-33714

9.7 KM · Unit Petroleum Company · Section with this well →

Base Red Beds3,915-1,293
Brown Dolomite3,915-1,293
Red Beds3,915-1,293
Heebner6,838-4,216
Base Heebner6,838-4,216
Douglas6,838-4,216
Kansas City8,072-5,450
Marmaton9,120-6,498

12 TOPS · FIRST 8

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