WELL · 42-451-32920 · DISTRICT 7
Bud #1
Tom Green County · Wildcat field · Vertical
Bud #1 (API 42-451-32920) is a plugged well in Tom Green County, plugged October 24, 2024, last operated by HW Operating LLC.
The RRC has issued one drilling permit, issued October 11, 2024, permitted to 7,200 ft.
It was permitted by HW Operating, LLC and has since transferred to HW Operating LLC on the wellbore schedule.
Operator of record
HW Operating LLC
Permitted by HW Operating, LLC; the EWA schedule now lists a different operator.
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | HW Operating, LLCOct 11, 2024 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,200
- total depth, ft
- 1
- permits on file
- Oct 11, 2024
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Oct 24, 2024
Surface location
31.108800, -100.186600
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Tom Green County.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 903182-99 | Drill | HW Operating, LLC | Oct 10, 2024 | Oct 11, 2024 | Oct 17, 2024 | 7,200 |
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-451-32920 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-451-32920 → 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.
Nearby wells and their tops
NEAREST 7 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbours can.
Chico42-095-32439
14.4 KM · HW Operating, LLC · Section with this well →
| Coleman Junction | 1,540 | 530 |
| Cisco | 2,250 | -180 |
| Canyon | 2,970 | -900 |
| Cross Cut Sand | 3,530 | -1,460 |
| Palo Pinto | 3,540 | -1,470 |
| Harkey Sand | 3,611 | -1,541 |
| Capps Lime | 4,102 | -2,032 |
| Strawn | — |
Chico42-095-32452
14.5 KM · HW Operating, LLC · Section with this well →
| Coleman Junction | 1,608 | 454 |
| Cisco | 2,572 | -510 |
| Canyon | 3,525 | -1,463 |
| Strawn | 4,067 | -2,005 |
Chico42-095-32444
14.6 KM · HW Operating, LLC · Section with this well →
| Coleman Junction | 1,565 | 450 |
| Cisco | 2,530 | -515 |
| Canyon | 3,470 | -1,455 |
| Strawn | 4,016 | -2,001 |
K-P42-095-32466
14.9 KM · HW Operating, LLC · Section with this well →
| Coleman Junction | 1,430 | 617 |
| Upper Cook Sand | 2,056 | -9 |
| Lower King Sand | 2,461 | -414 |
| Cisco | 2,474 | -427 |
| Canyon | — | |
| Strawn | — |
Chico42-095-32448
15.2 KM · HW Operating, LLC · Section with this well →
| Coleman Junction | 1,569 | 460 |
| Cisco | 2,524 | -495 |
| Canyon | 3,475 | -1,446 |
| Strawn | 4,019 | -1,990 |
| Capps | 4,060 | -2,031 |
Chico42-095-32449
15.3 KM · HW Operating, LLC · Section with this well →
| Coleman Junction | 1,585 | 457 |
| Cisco | 2,525 | -483 |
| Canyon | 3,510 | -1,468 |
| Strawn | 4,052 | -2,010 |
| Capps Lime | 4,096 | -2,054 |
Chico42-095-32464
15.5 KM · HW Operating, LLC · Section with this well →
| Coleman Junction | 1,492 | 572 |
| King Sand | 2,045 | 19 |
| Cisco | 2,528 | -464 |
| Canyon | 2,958 | -894 |
| Strawn | 4,000 | -1,936 |
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/45132920, documented in the API reference.