What this is

Every API number the Commission has assigned in Texas, with the identifying attributes that go with it, in fixed-width ASCII.

The Well API manual explains how Texas API numbers are constructed and assigned, which is worth reading before you trust any API join.

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 mirror the Commission's file exactly as they published it, byte for byte. We have not decoded this one into a table yet, so reading it needs the right tooling.

What we add

Validate API numbers against the authoritative assignment list, and find numbers that were assigned but never drilled.

  • Mirrored so the file is here when the Commission's own link is not.
  • Documented — what it is, where it came from, and when we last fetched it.

Worth knowing before you use it

An assigned API number is not a well. Assignment happens at permit time.

EZRRC does not parse this file. Upstream has not built a reader for it yet, so the catalog documents it and links to the Commission's own copy rather than pretending to serve rows it does not have.

The full page lists every trap in this dataset.

Get it

We have no copy of this one to give you yet — the Commission publishes it somewhere we cannot mirror byte for byte, or has stopped publishing it. The full page says which, and links to the Commission’s own copy where there is one.

People who want this usually want