WELLS · TEXAS · ONE ROW PER API NUMBER

Texas wells completed in the Cisco

Every well on the Railroad Commission's schedule or with a drilling permit on file, newest permit first: who operates it, where it is, the field it is completed in, its permits, and the last month its lease reported.What an API number is →

A full API number opens the well. Anything else filters the list below.

4 wells match

Texas reports production by lease, so a well carries no volumes of its own: "Last reported" is the last month the lease it is tied to reported. How Texas production is reported →

4 WELLS · PAGE 1 OF 1

These wells on a map →
WellOperatorCounty, fieldStatusDepth, ftPermitPermitsLast reported
Medford #342-207-32863G & F Oil Inc. HaskellRockdale (Cisco Lime)PluggedOil2,500Nov 10, 20141Jul 2026
Medford #242-207-32862G & F Oil Inc. HaskellRockdale (Cisco Lime)PluggedOil2,500Oct 24, 20141Jul 2026
Medford #142-207-32846G & F Oil Inc. HaskellRockdale (Cisco Lime)ActiveOil2,066Aug 26, 20141Jul 2026
Stasny Medford Unit #142-207-32801G & F Oil Inc. HaskellRockdale (Cisco Lime)ActiveOil2,086Nov 12, 20131Jun 2026

About this data

One row per API number: every well on the Railroad Commission wellbore schedule, and every API number a drilling permit names. Operator, field, status, and dates are the schedule's where it lists the well, the latest permit's otherwise. Permits on file counts every permit and amendment. Texas reports production by lease, so a well shows the last month its lease reported and no volumes. Nothing is estimated.

Developers: this page as JSON is GET /v1/data/wells?state=tx, documented in the API reference.