WELL · 42-177-34764 · DISTRICT 3

Romulus A #1H

Y

Gonzales County · Southern Bay (Eagle Ford) field · Producing  · Horizontal

Romulus A #1H (API 42-177-34764) is a horizontal well in Gonzales County operated by FW Eagle Ford I LLC, completed May 1, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 31, 2025, permitted to 14,500 ft.

It was permitted by Baytex Energy USA, Inc. and has since transferred to FW Eagle Ford I LLC on the wellbore schedule.

Completion filings report 9 formation tops, including Anacacho, Austin Chalk, Eagle Ford, Buda.

Its lease has reported 158K barrels of oil and 102K mcf of gas since May 2025, last reporting in July 2026.

Operator of record

FW Eagle Ford I LLC

Permitted by Baytex Energy USA, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Jan 15, 2026 · 46 permits on file · (800) 461-6054

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFW Eagle Ford I LLC
Production reportsFW Eagle Ford I, LLCthrough Apr 2026
Latest permitBaytex Energy USA, Inc.Jan 31, 2025

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

14,500
total depth, ft
1
permits on file
Jan 31, 2025
last permit issued
May 1, 2025
completed
158K
cumulative oil, bbl
102K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2025 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 1, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

29.646227, -97.137604

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Gonzales County.

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
Romulus A O-3-28248Southern Bay (Eagle Ford)FW Eagle Ford I, LLC1158K102KMay 2025 – Jul 2026

Oil, barrels lease total

Last 12 months 157,839 · prior 12 0

010K20K202420252026

Gas, mcf lease total

Last 12 months 102,270 · prior 12 0

05K10K15K202420252026

Chain of custody

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

  1. 1Baytex Energy USA, Inc.May 2025 → Dec 2025
  2. 2FW Eagle Ford I, LLCJan 2026 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
905567-99DrillBaytex Energy USA, Inc.Jan 29, 2025Jan 31, 2025Feb 24, 202514,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-28248————

Formation tops

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

FormationMD ftSubsea
Anacacho9,581-9,145
Austin ChalkAUSTIN CHALK - H2S9,812-9,376
Eagle FordEAGLE FORD - H2S10,512-10,076
BudaBUDA - H2S, DISPOSAL——
Carrizo——
EdwardsEDWARDS - H2S——
Navarro——
Reklaw——
WilcoxWILCOX - DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
10,80721,214Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,99712.251,055 S
5.521,3648.753,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. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Dec 10, 2025Jul 22, 2025Yes

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Romulus B42-177-34765

0.0 KM · Baytex Energy USA, Inc. · Section with this well →

Anacacho9,610-9,173
Austin Chalk9,838-9,401
Eagle Ford10,550-10,113
Navarro—
Edwards—
Wilcox—
Reklaw—
Carrizo—

9 TOPS · FIRST 8

Romulus C42-177-34766

0.0 KM · Baytex Energy USA, Inc. · Section with this well →

Anacacho9,631-9,194
Austin Chalk9,875-9,438
Eagle Ford10,582-10,145
Navarro—
Wilcox—
Reklaw—
Buda—
Edwards—

9 TOPS · FIRST 8

Remus A42-177-34767

0.1 KM · Baytex Energy USA, Inc. · Section with this well →

Anacacho9,495-9,062
Austin Chalk9,723-9,290
Eagle Ford10,405-9,972
Edwards—
Reklaw—
Wilcox—
Navarro—
Buda—

9 TOPS · FIRST 8

Remus B42-177-34768

0.1 KM · Baytex Energy USA, Inc. · Section with this well →

Anacacho9,455-9,022
Austin Chalk9,684-9,251
Eagle Ford10,363-9,930
Wilcox—
Buda—
Carrizo—
Edwards—
Navarro—

9 TOPS · FIRST 8

Ricartorn D42-149-33555

0.6 KM · Penn Virginia Oil & Gas, L.P. · Section with this well →

Anacacho8,997-8,521
Austin Chalk9,256-8,780
Eagle Ford9,844-9,368
Wilcox—
Glen Rose—
Unidentified Water Sand - Dispos—

Caracara Unit42-149-33490

0.6 KM · Penn Virginia Oil & Gas, L.P. · Section with this well →

Wilcox3,900-3,426
Austin Chalk9,842-9,368
Eagle Ford10,516-10,042
Unidentified Water Sand - Dispos—
Glen Rose—

Caracara Unit42-149-33488

0.6 KM · Penn Virginia Oil & Gas, L.P. · Section with this well →

Glen Rose—
Wilcox—
Unidentified Water Sand - Dispos—

Caracara Unit42-149-33487

0.6 KM · Penn Virginia Oil & Gas, L.P. · Section with this well →

Wilcox3,900-3,426
Austin Chalk9,873-9,399
Eagle Ford10,551-10,077
Glen Rose—
Unidentified Water Sand - Dispos—

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