FIELDS · TEXAS · FIELD 62781750

Moose (Wolfcamp)

Field · District 08 · Ector County and 1 more · Wolfcamp in every state →

Moose (Wolfcamp) is an RRC field with 4 leases on file reported by 11 operators, in Ector County.

In the 12 months reported through April 2026 it produced 7,732 mcf of gas, up 119% on the year before, from 2 leases reporting volume.

Diamondback E&P LLC holds the most, 3 leases and 145,067 barrels lifetime.

Lifetime, the field has reported 177,985 barrels of oil and 516,864 mcf of gas.

4
leases on file
2
leases reporting volume
11
operators, all time
1
active wellbores of 5 · 1 operators today
761
bbl oil, 12 months through Apr 2026 · +7%
7,732
Mcf gas, same 12 months · +119%
177,985
bbl oil, lifetime · 516,864 Mcf gas

Every well completed in it, searchable →

Reported production by month

Last 12 months 761 · prior 12 708(+7%)

01002003002017201820192020202120222023202420252026

Moose (Wolfcamp): Oil by month.

Operators

BY LIFETIME OIL ON THEIR LEASES · TOP 2

OperatorLeasesOil, bblGas, McfLast reported
Diamondback E&P LLC3145K516KJul 2026
Vision Oil and Gas LLC132.9K691Jul 2026

All 4 leases in Moose (Wolfcamp), searchable →

Counties

Latest completions

BY COMPLETION DATE

WellOperatorCountyCompletedTop perf, ftOil, 12 moGas, 12 mo
Ector -AG- Fee #2Diamondback E&P LLCEctorSep 25, 2018—00
Averitt F No. 1 #1HDiamondback E&P LLCEctorJan 9, 1998—00
Averitt W.T. III #1Diamondback E&P LLCEctorMay 19, 1995—00
Cowden J. Ellis #148Vision Oil and Gas LLCEctorJan 12, 1990—00

About this data

Field 62781750 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, Wolfcamp, is read from the field's name. Nothing is estimated.

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