TEXAS · WELLS · ZAPATA COUNTY · TREVINO LEASE · API 42-505-35102 · DISTRICT 04

Trevino #2

Y

Zapata County · Haynes (Hinnant Cons.) field · Producing  · Vertical

Fields on the latest permit · any of 2
Fandango, West · Haynes (Hinnant Cons.)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

Trevino #2 (API 42-505-35102) is a well in Zapata County operated by Hilcorp Energy Company, completed January 20, 2005 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued September 23, 2004, permitted to 15,500 ft.

It was permitted by Westport Oil And Gas Company, LP and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report 3 formation tops, including Hinnant 1, Hinnant 3, Wilcox.

Its lease has reported 5 barrels of oil and 820K mcf of gas since January 2005, last reporting volume in April 2026.

Operator of record

Hilcorp Energy Company

Permitted by Westport Oil and Gas Company, LP; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
Mar 27, 2026
Permits on file
3,458
Phone
(713) 209-2400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitWestport Oil and Gas Company, LPSep 23, 2004

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

15,500
total depth, ft
2
permits on file
Sep 23, 2004
last permit issued
Jan 20, 2005
completed
5
cumulative oil, bbl
820K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2005 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 20, 2005
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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Trevino G-4-208496Haynes (Hinnant Cons.)Hilcorp Energy Company15820KJan 2005 – Apr 2026

Gas, mcf lease total

Last 12 months 18,384 · prior 12 16,233(+13%)

01K2K3K202420252026

Chain of custody

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

  1. 1Westport Oil and Gas Company, LPJan 2005 → Feb 2006
  2. 2Kerr-McGee Oil & Gas Onshore LPMar 2006 → May 2007
  3. 3Southern G Holdings, LLCJun 2007 → Dec 2007
  4. 4Crimson Exploration Oper., Inc.Jan 2008 → Jan 2017
  5. 5Beehive Operating, LLCFeb 2017 → Dec 2022
  6. 6Bordertown Energy Resources, LLCJan 2023 → Aug 2023
  7. 7Hilcorp Energy CompanySep 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
551412-98DrillWestport Oil and Gas Company, LPMay 5, 2005Sep 23, 2004Nov 7, 200418,000
551412-99DrillWestport Oil and Gas Company, LPSep 23, 2004Sep 23, 2004—18,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 20, 2005Trevino G-4-208496Haynes (Hinnant Cons.)Hilcorp Energy CompanyProducing15,500

Formation tops

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

FormationMD ftSubsea
Hinnant 19,583-9,077
Hinnant 311,180-10,674
WilcoxWILCOX 1914,180-13,674

Perforations

Perforated and open-hole intervals.

FromToType
12,20712,230Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,20017.51,330 S
9.6258,17412.251,390 S
4.515,4508.51,780 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
00Aug 1, 2005Feb 25, 2005Yes
00Jun 6, 2005——

Well logs

2 logs loaded from the RRC's log index, the latest received Oct 2, 2008. Density, Neutron, 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 describedFiles Intervalft, as filedDatereceivedSizeMB
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Hinnant 1, Hinnant 3, WilcoxTIFF8,185 to 15,538Oct 2, 2008run Dec 20, 200412.8
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF75 to 1,831Sep 5, 2008run Nov 10, 20042.25

"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.

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