WELL · 42-107-32188 · DISTRICT 11
NE Ridge Upper Clearfork Unit #4655
Crosby County · Vertical
NE Ridge Upper Clearfork Unit #4655 (API 42-107-32188) is a permitted well in Crosby County filed by Surge Operating, LLC; no completion report is on file yet.
The RRC has issued one drilling permit, issued October 22, 2019, permitted to 5,000 ft.
Operator of record
Houston, TX · P-5 Y, filed May 4, 2026 · 1,234 permits on file · (832) 495-6024
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | none |
| Latest permit | Surge Operating, LLCOct 22, 2019 |
- 5,000
- total depth, ft
- 1
- permits on file
- Oct 22, 2019
- last permit issued
- —
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
Surface location
33.526763, -101.502729
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Crosby County.
Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 858117-99 | Drill | Surge Operating, LLC | Oct 16, 2019 | Oct 22, 2019 | — | 5,000 |
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-107-32188 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-107-32188 → scanned completion filings
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 has no tops filed, so it cannot anchor a section; its neighbours can.
Williams, Etal42-107-32187
1.5 KM · Surge Operating, LLC · Section with this well →
| Yates | 1,735 | 1,347 |
| San Andres | 2,788 | 294 |
| Glorieta | 3,952 | -870 |
| Clear Fork | 4,197 | -1,115 |
Caddell-1072, Etal42-107-31354
3.8 KM · Surge Operating, LLC · Section with this well →
| San Andres | 2,760 | 303 |
| Glorieta | 3,915 | -852 |
| Clear Fork | 4,122 | -1,059 |
A.L. Robertson 'D'42-107-32173
4.3 KM · Surge Operating, LLC · Section with this well →
| Yates | 1,762 | 1,298 |
| San Andres | 2,863 | 197 |
| Glorieta | 3,959 | -899 |
| Clear Fork | 4,310 | -1,250 |
Aycock42-107-32185
4.4 KM · Surge Operating, LLC · Section with this well →
| Yates | 1,740 | 1,299 |
| San Andres | 2,800 | 239 |
| Glorieta | 3,870 | -831 |
| Clear Fork | 4,250 | -1,211 |
Aycock, D.W.42-107-32184
4.4 KM · Surge Operating, LLC · Section with this well →
| Yates | 1,740 | 1,294 |
| San Andres | 2,800 | 234 |
| Glorieta | 3,870 | -836 |
| Clear Fork | 4,228 | -1,194 |
Clark Wood Ranch42-107-31675
4.8 KM · Surge Operating, LLC · Section with this well →
| Yates | 1,000 | 1,994 |
| Rustler | 1,253 | 1,741 |
| San Andres | 2,000 | 994 |
| Glorieta | 3,825 | -831 |
| Glorieta | 3,825 | -831 |
| Clear Fork | 4,092 | -1,098 |
| Clear Fork | 4,092 | -1,098 |
A.L. Robertson 'D'42-107-32171
5.0 KM · Surge Operating, LLC · Section with this well →
| Yates | 1,760 | 1,303 |
| San Andres | 2,830 | 233 |
| Glorieta | 3,950 | -887 |
| Clear Fork | 4,313 | -1,250 |
A.L. Robertson 'D'42-107-32174
5.1 KM · Surge Operating, LLC · Section with this well →
| Yates | 1,760 | 1,293 |
| San Andres | 2,835 | 218 |
| Glorieta | 3,896 | -843 |
| Clear Fork | 4,330 | -1,277 |
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/10732188, documented in the API reference.