FIELDS · TEXAS · FIELD 70134166

Pecos Valley, S. (Devonian)

Field · District 08 · Pecos County · Devonian in every state →

Pecos Valley, S. (Devonian) is an RRC field with 4 leases on file reported by 7 operators, in Pecos County.

In the 12 months reported through April 2026 it produced 2,378 barrels of oil, down 34% on the year before, from 1 lease reporting volume.

Olsen Energy Inc. holds the most, 2 leases and 151,310 barrels of oil lifetime.

Lifetime, the field has reported 169,925 barrels of oil and 1.1 million mcf of gas.

4
leases on file
1
leases reporting volume
7
operators, all time
2
active wellbores of 6 · 1 operators today
2,378
bbl oil, 12 months through Apr 2026 · −34%
305
Mcf gas, same 12 months · −64%
169,925
bbl oil, lifetime · 1.1M Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 2,378 · prior 12 3,598(-34%)

02004006002017201820192020202120222023202420252026

Pecos Valley, S. (Devonian): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 3

OperatorLeasesOil, bblGas, McfLast reported
Olsen Energy Inc.2151K795KJul 2026
Incline Energy114.3K258KAug 2019
Limark Corporation14.34K31.1KSep 2003

All 4 leases in Pecos Valley, S. (Devonian), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Iowa Realty Trust #1Olsen Energy Inc.PecosAug 3, 2012—00
Iowa Realty Trust B #1Incline EnergyPecosAug 5, 1991—00
Irt 21 #1TXO Production Corp.PecosSep 25, 1975—00

About this data

Field 70134166 from RRC PDQ lease reports: lifetime totals and lease and operator counts from the field summary; the monthly series summed from every lease report naming the field, cut at the statewide reported-through month, Apr 2026. Counties from the wells completed on each lease. Completions are the wellbores the RRC schedule ties to the field. The formation, Devonian, is read from the field's name. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/fields/tx/70134166, documented in the API reference.