WELL · 42-025-33769 · DISTRICT 2

Davis Nona Berry #67

Y

Bee County · Yougeen (Hockley 4500) field · Temp Abandoned  · Vertical

Davis Nona Berry #67 (API 42-025-33769) is a well in Bee County operated by Welderxp Ltd., completed July 13, 2011 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued June 3, 2011, permitted to 5,000 ft.

It was permitted by Welder Exploration & Prod., Inc. and has since transferred to Welderxp Ltd. on the wellbore schedule.

Completion filings report one formation top, including Hockley.

No lease production has been reported under this well’s leases.

Operator of record

Welderxp Ltd.

Permitted by Welder Exploration & Prod., Inc.; the EWA schedule now lists a different operator.

Based in
San Antonio, TX
P-5 status
Active (A)
P-5 last filed
Jan 29, 2026
Permits on file
14
Phone
(210) 354-1515

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWelderxp Ltd.
Production reportsWelderxp Ltd.through Dec 2023
Latest permitWelder Exploration & Prod., Inc.Jun 3, 2011

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

5,000
total depth, ft
2
permits on file
Jun 3, 2011
last permit issued
Jul 13, 2011
completed
0
cumulative oil, bbl
9.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 13, 2011
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Davis, Nona Berry G-2-262151Yougeen (Hockley 4500)Welderxp Ltd.109.9KJul 2011 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 0

0204060202420252026

Chain of custody

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

  1. 1Welder Exploration & Prod., Inc.Jul 2011 → Dec 2020
  2. 2Welderxp Ltd.Jul 2023 → Dec 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
717419-98DrillWelder Exploration & Prod., Inc.Aug 8, 2011Jun 3, 2011Jun 28, 20115,000
717419-99DrillWelder Exploration & Prod., Inc.May 31, 2011Jun 3, 2011Jun 28, 20115,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-262151————

Formation tops

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

FormationMD ftSubsea
Hockley4,560-4,326

Perforations

Perforated and open-hole intervals.

FromToType
4,5644,594Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62582512.25409 S
4.54,9007.875999 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
00Feb 13, 2012Sep 8, 2011Yes

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