EZRRC
Cart Sign in

Every Texas RRC dataset, in a format you can actually open.

The Railroad Commission publishes this data in 1970s mainframe formats. We decode it, join it, and hand it back to you as CSV, Excel, GeoPackage or KML — free.

Browse the catalog How this data works

As published One record from Drilling Permits — fixed-width, no headers, no delimiters
42383321450000MIDLAND G20240117PIONEER NATURAL RES 08

Apply the record layout

  1. api_number 42-383-32145 bytes 1–14
  2. county_name MIDLAND bytes 15–34
  3. well_code G Gas
  4. permit_date 2024-01-17 bytes 36–43
  5. district 08 Midland
Datasets
90
Rows mirrored
192.7M
Queryable now
47
Code lookups
456

Every section RRC publishes

  • Oil & Gas Field Data

    5 datasets

    The field name and number lookup, field rules, and annual field-level totals.

  • Underground Injection Control Data

    4 datasets

    Injection and disposal wells: permits, authorised volumes, monitoring and enforcement.

  • Oil & Gas Well Data

    26 datasets

    Wellbores, completions, plugging records and well tests.

  • Boundary Ventures Site

    1 dataset

    A one-time document release relating to the Boundary Ventures site.

  • Severance Tax Incentive Data

    4 datasets

    High-cost gas, tight sands and other severance-tax certifications.

  • Production Data

    27 datasets

    How much oil, gas, condensate and casinghead gas each lease produced, month by month.

  • Drilling Permit Data

    7 datasets

    Every application to drill a well in Texas, and what the Commission did with it.

  • Oil & Gas Regulatory Data

    9 datasets

    Who the operators are, what they are authorised to do, and what the Commission did about it.

  • Digital Map Data

    7 datasets

    County-by-county shapefiles of wells, surveys, pipelines and base map features.

Freshly mirrored

We watch the upstream loads and record what changed. These are the most recent versions we have observed.

Why this data is hard to use

The Railroad Commission publishes all of this for free. The problem was never access. It is that the files are written for a 1970s mainframe and everything needed to read them is somewhere else.

  • It is written for a mainframe

    18 of these datasets ship as EBCDIC, IBM's cp037 character set. Open one in a spreadsheet and you get punctuation soup. Every byte has to be transcoded before a single field is readable.

  • The column layout lives in a PDF

    38 more are fixed-width ASCII with no headers and no delimiters. The byte positions are published only in 36 scanned record-layout manuals. Miss one column by a single byte and every field after it is silently wrong.

  • The join keys are never named

    Nothing in the files tells you that permits meet wellbores on the API number, or that both meet operators on the P-5 number. We have mapped 57 joins between datasets and show you the exact columns on both sides.

  • The codes are not in the file

    A well type of G, a status of 03, a district of 7B. The meanings live in prose, in manuals, or nowhere. We hold 456 coded values across 29 lookup sets as real tables, so you can read the labels or join them into your export.

How EZRRC handles it