WELL · 42-433-33823 · DISTRICT 7
Vacca Wedeking #1
Stonewall County · Flowers (Canyon Sand) field · Producing · Vertical
Vacca Wedeking #1 (API 42-433-33823) is a well in Stonewall County operated by Texas Royalty Corp., completed July 13, 2012 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued May 14, 2012, permitted to 4,500 ft.
Completion filings report 3 formation tops, including Gunsight, Cisco, Canyon.
Its lease has reported 11.4K barrels of oil since July 2012, last reporting in July 2026.
Operator of record
- Based in
- Austin, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Mar 3, 2026
- Permits on file
- 88
- Phone
- (512) 306-1717
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Texas Royalty Corp. |
| Production reports | Texas Royalty Corp.through Mar 2026 |
| Latest permit | Texas Royalty Corp.May 14, 2012 |
- 4,500
- total depth, ft
- 1
- permits on file
- May 14, 2012
- last permit issued
- Jul 13, 2012
- completed
- 11.4K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2012 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jul 13, 2012
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (X)
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Vacca Wedeking O-8-31057 | Flowers (Canyon Sand) | Texas Royalty Corp. | 1 | 11.4K | 0 | Jul 2012 – Jul 2026 |
Oil, barrels lease total
Last 12 months 403 · prior 12 554(-27%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Texas Royalty Corp.Aug 2012 → Mar 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 739717-99 | Drill | Texas Royalty Corp. | May 1, 2012 | May 14, 2012 | Jun 29, 2012 | 4,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-8-31057 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,786 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,172 | 4,177 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 177 | 12.25 | 130 S |
| 5.5 | 4,358 | 7.875 | 165 S |
| 5.5 | — | 16.625 | 765 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Nov 29, 2012 | Aug 21, 2012 | Yes |
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.
- Wellbore filings for 42-433-33823 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-433-33823 → scanned completion filings
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/43333823, documented in the API reference.