WELL · 42-507-32649 · DISTRICT 1
Raine #8
Zavala County · Independence West (Olmos 3900) field · Vertical
Raine #8 (API 42-507-32649) is a plugged well in Zavala County, plugged July 7, 2014, last operated by Bridger Oil Inc..
The RRC has issued one drilling permit, issued August 17, 2004, permitted to 3,500 ft.
Completion filings report one formation top, including Olmos.
Its lease has reported 50.5K barrels of oil and 282 mcf of gas since January 1993, last reporting in January 2017. The lease carries 3 wells, so these are lease totals, not this well alone.
Operator of record
Richmond, TX · P-5 Y, filed Jul 4, 2026 · 15 permits on file · (713) 259-2150
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Bridger Oil Inc. |
| Production reports | Bridger Oil Inc.through Oct 2016 |
| Latest permit | Bridger Oil Inc.Aug 17, 2004 |
- 3,500
- total depth, ft
- 1
- permits on file
- Aug 17, 2004
- last permit issued
- Aug 1, 2005
- completed
- 50.5K
- cumulative oil, bbl
- 282
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2017
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 1, 2005
- Shut in
- —
- Plugged
- Jul 7, 2014
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Raine O-1-6437 | Independence, West (Olmos 3900) | Bridger Oil Inc. | 3 | 50.5K | 282 | Jan 1993 – Jan 2017 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Bridger Oil Inc.Jan 1993 → Oct 2014
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 549595-99 | Drill | Bridger Oil Inc. | Aug 13, 2004 | Aug 17, 2004 | Nov 10, 2004 | 3,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-6437 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 687 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Olmos | 3,320 | -2,633 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,320 | 3,334 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 330 | 12.25 | 220 S |
| 4.5 | 3,330 | 7.875 | 335 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 | Sep 1, 2006 | Jul 20, 2005 | Yes |
| 00 | Jan 13, 2006 | — | — |
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-507-32649 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-507-32649 → 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/50732649, documented in the API reference.