TEXAS · WELLS · REEVES COUNTY · FILMORE 25 LEASE · API 42-389-33417 · DISTRICT 7B

Filmore 25 #1

Shut in

Reeves County · Wolfbone (Trend Area) field · Shut In  · Vertical

Filmore 25 #1 (API 42-389-33417) is a well in Reeves County operated by Permian Resources Operating LLC, completed January 31, 2013 and listed as shut in on the RRC schedule, shut in May 1, 2023.

The RRC has issued one drilling permit, issued August 3, 2012, permitted to 11,900 ft.

It was permitted by Thompson, J. Cleo and has since transferred to Permian Resources Operating LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Bone Spring, Wolfcamp.

Its lease has reported 49.8K barrels of oil and 64.5K mcf of gas since November 2012, with no volume in the three years through April 2026.

Operator of record

Permian Resources Operating LLC

Permitted by Thompson, J. Cleo; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Nov 25, 2025
Permits on file
608
Phone
(432) 695-4222

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePermian Resources Operating LLC
Production reportsPermian Resources Operating, LLCthrough Dec 2022
Latest permitThompson, J. CleoAug 3, 2012

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

11,900
total depth, ft
1
permits on file
Aug 3, 2012
last permit issued
Jan 31, 2013
completed
49.8K
cumulative oil, bbl
64.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2012 THROUGH Dec 2022

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 31, 2013
Shut in
May 1, 2023
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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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
Filmore 25 O-10-43635Wolfbone (Trend Area)Permian Resources Operating, LLC149.8K64.5KNov 2012 – Dec 2022

No volumes reported on these leases in the last three years.

Wells named Filmore 25

Permian Resources Operating LLC's other wells filed under this lease name in Reeves County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Thompson, J. CleoDec 2012 → Mar 2013
  2. 2OXY USA WTP LPApr 2013 → Sep 2018
  3. 3Noble Energy IncNov 2018 → Aug 2022
  4. 4Colgate Operating, LLCOct 2022 → Dec 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
745265-99DrillThompson, J. CleoJul 24, 2012Aug 3, 2012Oct 15, 201213,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 31, 2013Filmore 25 O-10-43635Wolfbone (Trend Area)Permian Resources Operating LLCShut In · shut in May 1, 202311,900

Formation tops

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

FormationMD ftSubsea
Bone Spring2ND BONE SPRINGS9,722-7,067
Bone Spring3RD BONE SPRINGS10,522-7,867
Wolfcamp11,772-9,117

Perforations

Perforated and open-hole intervals.

FromToType
9,27610,673Open hole
10,73111,690Perforated
10,73111,690Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37554517.5600 S
8.6255,15911925 S
5.511,9007.8751,400 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Feb 11, 2014May 1, 2013—
00Jan 6, 2014Jan 8, 2013Yes

Well logs

1 log loaded from the RRC's log index, the latest received Dec 8, 2015. Neutron. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
NEUTRON POROSITYSpans Bone Spring, WolfcampTIFF5,000 to 11,792Dec 8, 2015run Nov 27, 20124.10

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/38933417, documented in the API reference.