WELL · 42-161-33807 · DISTRICT 5

Horton #2

Y

Freestone County · Nan-SU-Gail (CV Consolidated) field · Producing  · Vertical

Horton #2 (API 42-161-33807) is a well in Freestone County operated by Stroud Petroleum Inc., completed June 1, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 25, 2007, permitted to 12,900 ft.

It was permitted by Reserve Management, Inc. and has since transferred to Stroud Petroleum Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Pettit, Travis Peak, Cotton Valley, Bossier.

No lease production has been reported under this well’s leases.

Operator of record

Stroud Petroleum Inc.

Permitted by Reserve Management, Inc.; the EWA schedule now lists a different operator.

Shreveport, LA · P-5 Y, filed Nov 4, 2025 · 165 permits on file · (318) 425-0101

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleStroud Petroleum Inc.
Production reportsStroud Petroleum, Inc.through Apr 2026
Latest permitReserve Management, Inc.Jan 25, 2007

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

12,900
total depth, ft
1
permits on file
Jan 25, 2007
last permit issued
Jun 1, 2007
completed
0
cumulative oil, bbl
602K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 1, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Horton G-5-229546Nan-SU-Gail (CV Consolidated)Stroud Petroleum, Inc.10602KJun 2007 – Jul 2026

Gas, mcf lease total

Last 12 months 5,489 · prior 12 4,762(+15%)

01K2K202420252026

Chain of custody

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

  1. 1Reserve Management, Inc.Jun 2007 → Jan 2016
  2. 2Stroud Petroleum, Inc.Feb 2016 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
632359-99DrillReserve Management, Inc.Jan 23, 2007Jan 25, 2007Apr 1, 200712,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-5-229546————

Formation tops

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

FormationMD ftSubsea
Pettit8,878-8,335
Travis Peak9,110-8,567
Cotton Valley10,550-10,007
Bossier12,520-11,977

Perforations

Perforated and open-hole intervals.

FromToType
12,69212,917Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,63912.251,048 S
4.512,9407.875538 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
00Oct 3, 2007Jun 26, 2007Yes
00Sep 21, 2007——

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.

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