WELL · 42-329-35952 · DISTRICT 8

Wimberley 1 #1

Y

Midland County · Spraberry (Trend Area) field · Producing  · Vertical

Wimberley 1 #1 (API 42-329-35952) is a well in Midland County operated by Midland Energy Inc., completed September 20, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued May 29, 2008, permitted to 11,300 ft.

Completion filings report 6 formation tops, including San Andres, Clear Fork, Spraberry, Dean.

Its lease has reported 253K barrels of oil and 474K mcf of gas since September 2009, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Midland Energy Inc.

Midland, TX · P-5 Y, filed Jan 5, 2026 · 105 permits on file · (432) 687-2222

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMidland Energy Inc.
Production reportsMidland Energy, Inc.through Apr 2026
Latest permitMidland Energy, Inc.Jun 23, 2008
11,300
total depth, ft
2
permits on file
Jun 23, 2008
last permit issued
Sep 20, 2009
completed
253K
cumulative oil, bbl
474K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 20, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Wimberley "1" O-10-40013Spraberry (Trend Area)Midland Energy, Inc.3253K474KSep 2009 – Jul 2026

Oil, barrels lease total

Last 12 months 6,692 · prior 12 7,181(-7%)

05001K202420252026

Gas, mcf lease total

Last 12 months 0 · prior 12 26,003(-100%)

02K4K6K202420252026

Chain of custody

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

  1. 1Midland Energy, Inc.Oct 2009 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
663098-98DrillMidland Energy, Inc.Jun 23, 2008Jun 23, 2008Aug 20, 200911,300
663098-99DrillMidland Energy, Inc.May 28, 2008May 29, 2008Aug 20, 200911,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-40013————

Formation tops

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

FormationMD ftSubsea
San AndresBASE SAN ANDRES5,150-2,359
Clear ForkBASE CLEARFORK7,025-4,234
Spraberry7,800-5,009
Dean9,125-6,334
Wolfcamp9,350-6,559
Strawn10,450-7,659

Perforations

Perforated and open-hole intervals.

FromToType
7,9839,291Perforated
9,35610,438Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
12.7536617.5410 S
8.6255,31811450 S
5.511,3227.8751,250 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
00Aug 10, 2010Apr 29, 2010Yes
00Jul 14, 2010——

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