WELL · 42-365-35785 · DISTRICT 6
Bristol #2
Panola County · Belle Bower (Paluxy Upper) field · Temp Abandoned · Vertical
Bristol #2 (API 42-365-35785) is a permitted well in Panola County filed by Paladin Drilling Company; no completion report is on file yet.
The RRC has issued one drilling permit, issued June 13, 2005, permitted to 3,400 ft.
It was permitted by Paladin Drilling Company and has since transferred to Brammer Petroleum Inc. on the wellbore schedule.
Completion filings report 2 formation tops, including Fredericksburg, Paluxy.
Operator of record
Permitted by Paladin Drilling Company; the EWA schedule now lists a different operator.
Gainesville, TX · P-5 Y, filed Nov 4, 2025 · 11 permits on file · (940) 736-1165
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Brammer Petroleum Inc. |
| Production reports | none |
| Latest permit | Paladin Drilling CompanyJun 13, 2005 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 3,400
- total depth, ft
- 1
- permits on file
- Jun 13, 2005
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2005 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- —
- 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Bristol G-6-219184 | Belle Bower (Paluxy Upper) | Brammer Petroleum, Inc. | 1 | 0 | 0 | Jul 2005 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 601984-99 | Drill | Paladin Drilling Company | Jun 13, 2005 | Jun 13, 2005 | Jun 28, 2005 | 3,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-6-219184 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 313 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Fredericksburg | 2,730 | -2,417 |
| PaluxyPALUXY UPPER | 3,070 | -2,757 |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 549 | 11 | 210 S |
| 4.5 | 3,310 | 7.875 | 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Feb 9, 2007 | Mar 10, 2006 | Yes |
| 00 | Sep 20, 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-365-35785 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-365-35785 → 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/36535785, documented in the API reference.