WELL · 42-161-32575 · DISTRICT 5

Eubanks Unit No. 1 #8

N

Freestone County · Freestone (Bossier Sand) field  · Vertical

Eubanks Unit NO. 1 #8 (API 42-161-32575) is a well in Freestone County operated by Xto Energy Inc., completed June 6, 2003.

The RRC has issued one drilling permit, issued February 4, 2003, permitted to 13,500 ft.

Completion filings report 5 formation tops, including BMA, Pettit, Travis Peak, Cotton Valley.

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

Operator of record

XTO Energy Inc.

Based in
Spring, TX
P-5 status
Active – Extension (X)
P-5 last filed
Apr 8, 2026
Permits on file
16,156
Phone
(346) 502-1572

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsHilcorp Energy Companythrough Dec 2025
Latest permitXTO Energy Inc.Feb 4, 2003

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

13,500
total depth, ft
1
permits on file
Feb 4, 2003
last permit issued
Jun 6, 2003
completed
0
cumulative oil, bbl
1.94M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 6, 2003
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Eubanks Unit No. 1 G-5-196243Freestone (CV-Bossier Cons.)Hilcorp Energy Company101.94MJun 2003 – Jul 2026
Eubanks Unit No. 1 G-5-196245Freestone (Bossier Sand)XTO Energy Inc.100Jun 2003 – Feb 2006

Gas, mcf lease total

Last 12 months 22,409 · prior 12 10,694(+110%)

02K4K6K202420252026

Chain of custody

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

  1. 1XTO Energy Inc.Jun 2003 → Dec 2023
  2. 2Hilcorp Energy CompanyJan 2024 → Dec 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
528772-99DrillXTO Energy Inc.Feb 21, 2003Feb 4, 2003Apr 7, 200313,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-196243————
—— G-5-196245————

Formation tops

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

FormationMD ftSubsea
BMA7,364-6,923
Pettit8,028-7,587
Travis Peak8,258-7,817
Cotton ValleyCOTTON VALLEY SAND10,307-9,866
Bossier11,325-10,884
Cotton ValleyCOTTON VALLEY LIME12,458-12,017

Perforations

Perforated and open-hole intervals.

FromToType
11,51011,661Perforated
11,51012,638Perforated
12,50112,638Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,48012.25735 S
5.512,8218.751,875 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 7, 2006Apr 28, 2006—
00Sep 11, 2003Jul 14, 2003Yes
00Sep 4, 2003——

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