EZRRC
Cart Sign in

Completion Information in Data Format

Forms G-1 and W-2: the filings that turn a drilled hole into a producing well.

What this is

The completion packet, published nightly. Each packet is a header — operator, lease, field, well, API number, dates, depths, the initial potential test — followed by repeating rows for casing strings, formation tops, production intervals and the materials pumped during stimulation.

EZRRC parses the packet into a header table plus four child tables and publishes each child separately, so the stimulation-materials rows — the closest thing Texas has to a …

How it is laid out

The Railroad Commission publishes this as Fixed-width ASCII. Columns are byte ranges with no separators, described only in a scanned record layout. We decode it into a table you can open anywhere. It has 101 columns and about 524.2K rows.

The columns you will most likely want:

  • tracking_no The completion packet's RRC tracking number.
  • file_batch_date The nightly batch this packet arrived in. RRC publishes completions as one zip per day, so this is …
  • tracking_no The completion packet's RRC tracking number.
  • tracking_no The completion packet's RRC tracking number.
  • tracking_no The completion packet's RRC tracking number.
  • packet_id Identifier of the completion packet this row belongs to.

…and 95 more, all documented on the full page.

What we add

See a well's initial potential test: oil, gas and water rates, choke size, gravity and calculated 24-hour rate.

Find recently completed wells by spud, work-completed or completion date, and track how long operators are taking between spud and first production.

Pull the stimulation record — …

  • Decoded out of the Commission's original format into something Excel opens.
  • Filterable before you download, so you can take one county instead of the whole state.
  • The Commission's single-letter codes translated into words.
  • Mapped — download it straight into Google Earth or QGIS.

Worth knowing before you use it

This file writes the API number as eight fused digits (county then unique) with no state prefix and no dashes, while the permit and wellbore files write it as 42-XXX-XXXXX. They do not join without reformatting.

Numeric measurements are stored as text exactly as filed, so depths and rates can contain blanks, ranges and notes. …

The full page lists every trap in this dataset.

Get it

People who want this usually want