TEXAS · WELLS · DIMMIT COUNTY · BRISCOE FRIDAY RANCH LEASE · API 42-127-34807 · DISTRICT 01
Briscoe Friday Ranch #25H
Dimmit County · Briscoe Ranch (Eagleford) field · Producing · Horizontal
Briscoe Friday Ranch #25H (API 42-127-34807) is a horizontal well in Dimmit County operated by Javelin Energy Partners Mgmt LLC, completed February 26, 2013 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued May 18, 2012, permitted to 8,284 ft.
It was permitted by Anadarko E&P Company LP and has since transferred to Javelin Energy Partners Mgmt LLC on the wellbore schedule.
Completion filings report 3 formation tops, including Olmos, San Miguel, Eagle Ford.
Its lease has reported 142K barrels of oil and 2.2M mcf of gas since August 2012, last reporting volume in April 2026.
Operator of record
Javelin Energy Partners Mgmt LLC
Permitted by Anadarko E&P Company LP; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Feb 24, 2026
- Permits on file
- 234
- Phone
- (469) 575-3800
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Javelin Energy Partners Mgmt LLC |
| Production reports | Javelin Energy Partners Mgmt LLCthrough Apr 2026 |
| Latest permit | Anadarko E&P Company LPMay 18, 2012 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,284
- total depth, ft
- 2
- permits on file
- May 18, 2012
- last permit issued
- Feb 26, 2013
- completed
- 142K
- cumulative oil, bbl
- 2.2M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Mar 2013 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Feb 26, 2013
- 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 |
|---|---|---|---|---|---|---|
| Briscoe Friday Ranch G-1-269280 | Briscoe Ranch (Eagleford) | Javelin Energy Partners Mgmt LLC | 1 | 142K | 2.2M | Aug 2012 – Apr 2026 |
Gas, mcf lease total
Last 12 months 63,699 · prior 12 93,203(-32%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Anadarko E&P Onshore LLCMar 2013 → Feb 2017
- 2SN EF Maverick, LLCMar 2017 → Aug 2023
- 3Javelin Energy Partners Mgmt LLCSep 2023 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 740388-98 | Drill | Anadarko E&P Company LP | Jul 30, 2012 | May 18, 2012 | Aug 19, 2012 | 9,000 |
| 740388-99 | Drill | Anadarko E&P Company LP | May 10, 2012 | May 18, 2012 | — | 9,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Feb 26, 2013 | Briscoe Friday Ranch G-1-269280 | Briscoe Ranch (Eagleford) | Javelin Energy Partners Mgmt LLC | Producing | 8,284 |
Formation tops
As filed on W-2/G-1. Subsea from 553 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Olmos | 4,808 | -4,255 |
| San Miguel | 5,585 | -5,032 |
| Eagle FordEAGLEFORD | 7,948 | -7,395 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,410 | 14,662 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,965 | 12.25 | 627 S |
| 5.5 | 14,825 | 8.75 | 3,293 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 | Aug 20, 2013 | Jun 24, 2013 | — |
| 00 | Aug 15, 2013 | Nov 26, 2012 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Sep 10, 2015. Resistivity. 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 |
|---|---|---|---|---|
| RESISTIVITYSpans San Miguel, Eagle Ford | TIFF | 7,051 to 14,825 | Sep 10, 2015run Aug 28, 2012 | 1.63 |
"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-127-34807 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-127-34807 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/12734807, documented in the API reference.