TEXAS · WELLS · TERRELL COUNTY · GEASLIN NW "187" LEASE · API 42-443-31147 · DISTRICT 6E
Geaslin NW 187 #67
Terrell County · Geaslin (Wolfcamp) field · Producing · Vertical
Geaslin NW 187 #67 (API 42-443-31147) is a well in Terrell County operated by Brp Energy LLC, completed July 24, 2006 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued March 1, 2006, permitted to 6,460 ft.
It was permitted by Fasken Oil And Ranch, Ltd. and has since transferred to Brp Energy LLC on the wellbore schedule.
Completion filings report 5 formation tops, including C4, C3, B2, A3.
Its lease has reported 6 barrels of oil and 240K mcf of gas since July 2006, last reporting volume in April 2026.
Operator of record
Permitted by Fasken Oil and Ranch, Ltd.; the EWA schedule now lists a different operator.
- Based in
- San Angelo, TX
- P-5 status
- Active (A)
- P-5 last filed
- Oct 7, 2025
- Phone
- (325) 277-9743
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | BRP Energy LLC |
| Production reports | BRP Energy, LLCthrough Apr 2026 |
| Latest permit | Fasken Oil and Ranch, Ltd.Mar 1, 2006 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 6,460
- total depth, ft
- 2
- permits on file
- Mar 1, 2006
- last permit issued
- Jul 24, 2006
- completed
- 6
- cumulative oil, bbl
- 240K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jul 2006 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jul 24, 2006
- 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Geaslin NW "187" G-9-220666 | Geaslin (Wolfcamp) | BRP Energy, LLC | 1 | 6 | 240K | Jul 2006 – Apr 2026 |
Gas, mcf lease total
Last 12 months 540 · prior 12 0
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Fasken Oil and Ranch, Ltd.Jul 2006 → Mar 2021
- 2BRP Energy, LLCApr 2021 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 614785-98 | Drill | Fasken Oil and Ranch, Ltd. | Apr 5, 2006 | Mar 1, 2006 | — | 7,500 |
| 614785-99 | Drill | Fasken Oil and Ranch, Ltd. | Feb 23, 2006 | Mar 1, 2006 | Jun 28, 2006 | 7,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jul 24, 2006 | Geaslin NW 187 G-9-220666 | Geaslin (Wolfcamp) | BRP Energy LLC | Producing | 6,460 |
Formation tops
As filed on W-2/G-1. Subsea from 2,394 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| C4 | 5,103 | -2,709 |
| C3 | 5,216 | -2,822 |
| B2 | 5,656 | -3,262 |
| A3 | 5,986 | -3,592 |
| Quachita Seal | 6,163 | -3,769 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,218 | 5,228 | Perforated |
| 5,672 | 5,688 | Perforated |
| 6,346 | 6,353 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,468 | 12.25 | 505 S |
| 4.5 | 6,457 | 7.875 | 600 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Mar 6, 2007 | Aug 9, 2006 | Yes |
| 00 | Nov 1, 2006 | — | — |
Well logs
2 logs loaded from the RRC's log index, the latest received Jul 20, 2009. Cased hole, Density, 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 described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| SURVEYS CASED HOLESpans C4, C3, B2, A3, Quachita Seal | TIFF | 4,800 to 6,403 | Jul 20, 2009run Jul 17, 2006 | 0.88 |
| NEUTRON/DENSITY POROSITYSpans C4, C3, B2, A3, Quachita Seal | TIFF | 0 to 6,444 | Jul 20, 2009run Jul 7, 2006 | 3.17 |
"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.
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-443-31147 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-443-31147 → scanned completion filings
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/44331147, documented in the API reference.