WELL · 42-365-35630 · DISTRICT 6

Bristol #1

Y

Panola County · Belle Bower (Paluxy Upper) field · Producing  · Vertical

Bristol #1 (API 42-365-35630) is a well in Panola County operated by Brammer Petroleum Inc., completed July 21, 2005 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 27, 2005, permitted to 4,400 ft.

It was permitted by Eason Production Company and has since transferred to Brammer Petroleum Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Fredericksburg, Paluxy.

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

Operator of record

Brammer Petroleum Inc.

Permitted by Eason Production 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 scheduleBrammer Petroleum Inc.
Production reportsBrammer Petroleum, Inc.through Mar 2026
Latest permitEason Production CompanyJan 27, 2005

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

4,400
total depth, ft
1
permits on file
Jan 27, 2005
last permit issued
Jul 21, 2005
completed
0
cumulative oil, bbl
52.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 21, 2005
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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bristol G-6-216163Belle Bower (Paluxy Upper)Brammer Petroleum, Inc.1052.4KJul 2005 – Jul 2026

Gas, mcf lease total

Last 12 months 26,237 · prior 12 19,203(+37%)

02K4K202420252026

Chain of custody

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

  1. 1Paladin Drilling CompanyNov 2005 → Feb 2008
  2. 2Brammer Petroleum, Inc.Jun 2024 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
556381-99DrillEason Production CompanyJan 18, 2005Jan 27, 2005Apr 28, 20054,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-216163————

Formation tops

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

FormationMD ftSubsea
Fredericksburg2,700-2,405
PaluxyPALUXY UPPER3,060-2,765
PaluxyPALUXY LOWER3,150-2,855

Perforations

Perforated and open-hole intervals.

FromToType
3,0623,064Perforated
3,1883,191Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62554012.25310 S
4.53,4277.875250 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
00Sep 25, 2006Nov 28, 2005Yes
00Jun 5, 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.

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