TEXAS · WELLS · NACOGDOCHES COUNTY · API 42-347-32673 · DISTRICT 06

Trawick GU 17 #10

Y

Nacogdoches County · Trawick (Pettit-TP Cons.) field · Producing  · Vertical

Trawick GU 17 #10 (API 42-347-32673) is a well in Nacogdoches County operated by Urban Oil & Gas Group LLC, completed February 12, 2008 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 31, 2007, permitted to 8,900 ft.

It was permitted by Exxon Mobil Corporation and has since transferred to Urban Oil & Gas Group LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Rodessa, James Lime, Pettit, Travis Peak.

Its 2 leases have reported 73 barrels of oil and 1.29M mcf of gas since February 2008, last reporting volume in April 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Urban Oil & Gas Group LLC

Permitted by Exxon Mobil Corporation; the EWA schedule now lists a different operator.

Based in
Plano, TX
P-5 status
Active (A)
P-5 last filed
Dec 3, 2025
Permits on file
140
Phone
(972) 543-8800

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleUrban Oil & Gas Group LLC
Production reportsUrban Oil & Gas Group, LLCthrough Apr 2026
Latest permitExxon Mobil CorporationOct 31, 2007

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

8,900
total depth, ft
1
permits on file
Oct 31, 2007
last permit issued
Feb 12, 2008
completed
73
cumulative oil, bbl
1.29M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2008 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 12, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Trawick GU 17 G-6-236055Trawick (Pettit-TP Cons.)Urban Oil & Gas Group, LLC1731.25MFeb 2008 – Apr 2026
Trawick GU 17 G-6-239077Trawick (Pettit)Exxon Mobil Corporation1041.5KMay 2008 – Oct 2008

Gas, mcf lease total

Last 12 months 4,362 · prior 12 7,348(-41%)

05001K202420252026

Chain of custody

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

  1. 1Exxon Mobil CorporationFeb 2008 → Dec 2013
  2. 2XTO Energy Inc.Jan 2014 → Jan 2025
  3. 3Urban Oil & Gas Group, LLCFeb 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
647536-99DrillExxon Mobil CorporationOct 10, 2007Oct 31, 2007Dec 24, 20079,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 12, 2008Trawick GU 17 G-6-236055Trawick (Pettit-TP Cons.)Urban Oil & Gas Group LLCProducing8,900
May 16, 2008Trawick GU 17 G-6-239077Trawick (Pettit)Exxon Mobil CorporationNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Rodessa6,810-6,399
James Lime7,286-6,875
Pettit7,522-7,111
PettitPETTIT (TRANSITION ZONE)7,927-7,516
Travis Peak8,040-7,629
TD (Within Travis Peak)8,900-8,489

Perforations

Perforated and open-hole intervals.

FromToType
7,7948,012Perforated
8,3058,092Perforated
8,7088,360Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,17112.251,670 S
4.58,8928.75989 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
00Oct 3, 2008Jun 23, 2008Yes
00Sep 19, 2008——
00Jul 3, 2008Mar 17, 2008Yes
00Jun 13, 2008——

Well logs

2 logs loaded from the RRC's log index, the latest received Sep 29, 2008. Cased hole, 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
SURVEYS CASED HOLESpans Rodessa, James Lime, Pettit, Travis Peak, Td (Within Travis Peak)TIFF4,175 to 8,909Sep 29, 2008run Jan 4, 20080.45
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Rodessa, James Lime, Pettit, Travis Peak, Td (Within Travis Peak)TIFF4,175 to 8,909Sep 25, 2008run Jan 4, 20083.17

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