TEXAS · WELLS · MONTAGUE COUNTY · COLLIER, T. M. (5-9) LEASE · API 42-337-02397 · DISTRICT 7C

Collier T. M. (5-9) #7

Y

Montague County · Dyemound (Bend Conglomerate) field · Producing  · Vertical

Collier T. M. (5-9) #7 (API 42-337-02397) is a permitted well in Montague County filed by Hep Oil Company, Ltd.; no completion report is on file yet.

The RRC has issued one drilling permit, issued February 11, 2003, permitted to 6,570 ft.

It was permitted by Hep Oil Company, Ltd. and has since transferred to W&W Oil And Gas Inc. on the wellbore schedule.

Its lease has reported 29.4K barrels of oil and 84.3K mcf of gas since January 1993, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

W&W Oil and Gas Inc.

Permitted by Hep Oil Company, Ltd.; the EWA schedule now lists a different operator.

Based in
Muenster, TX
P-5 status
Active (A)
P-5 last filed
Jun 22, 2026
Phone
(940) 872-7542

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsW&W Oil and Gas, Inc.through Apr 2026
Latest permitHep Oil Company, Ltd.Feb 11, 2003
6,570
total depth, ft
1
permits on file
Feb 11, 2003
last permit issued
—
completed
29.4K
cumulative oil, bbl
84.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
—
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Collier, T. M. (5-9) O-13-4447Dyemound (Bend Conglomerate)W&W Oil and Gas, Inc.429.4K84.3KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 469 · prior 12 464(+1%)

050100202420252026

Chain of custody

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

  1. 1Burk Royalty CompanyJan 1993 → Feb 2000
  2. 2Brammer Supply, Inc.Mar 2000 → Oct 2001
  3. 3Hep Oil Company, Ltd.Nov 2001 → Dec 2007
  4. 4Hep Oil GP, LLCJan 2008 → Jan 2012
  5. 5Silver Creek Resources, LLCFeb 2012 → Aug 2012
  6. 6Silver Creek Oil & Gas, LLCSep 2012 → Dec 2012
  7. 7Felderhoff Production CompanyJan 2013 → Apr 2021
  8. 8Tettleton, Steven B.May 2021 → Jul 2021
  9. 9W&W Oil and Gas, Inc.Aug 2021 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
528260-99RecompletionHep Oil Company, Ltd.Feb 7, 2003Feb 11, 2003—7,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—Collier T. M. (5-9) O-13-4447Dyemound (Bend Conglomerate)W&W Oil and Gas Inc.Producing6,570

Perforations

Perforated and open-hole intervals.

FromToType
—6,570Perforated

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
00Jan 12, 1984——

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