Get the data

Free. You will be asked to confirm an email address before the files are built — that is the only gate, and it is there so we can tell you when a large export is ready.

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.

RRC publishes it twice a week as one dated subfolder per publication -- 470 of them on 2026-08-17, from 2020-09-02 to 2026-07-29 -- each holding 276 files named maf016.ccNNN, one per county code from 001 to 507 plus the offshore blocks. A listing of the folder's top level shows none of them, which is why this catalogue called the folder empty four times in August 2026. It was not; the files sit one level down.

First mirrored here on 2026-08-23, from the 2026-07-29 snapshot. RRC published 276 files that day and this holds 275 of them: maf016.cc712 was zero bytes, and the archiver will not write an empty object as a revision of anything. Nothing is lost -- an empty county file carries no API numbers -- but the count is one short of RRC's on purpose, and that is worth knowing before you compare them. 571,493,422 bytes in total.

What you can do with it

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

Gotchas

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

This is the ASCII edition, mirrored as the Commission publishes it: 276 fixed-width files, one per county code. If you want the same data as ROWS -- filterable, previewable, exportable in every format this site offers -- take the dBase edition instead. It is the same MAF016 extract, decoded into 1,556,119 entries covering 1,198,492 distinct API numbers, and it is linked from this page.

The reason to come here rather than there is that this is the Commission's own bytes. Nothing has parsed, renamed or reshaped them.

Record layout

0 columns.

We have not transcribed the record layout for this dataset yet. The RRC manual linked under “Where this comes from” is the authoritative description in the meantime.

Where this comes from

Published by

Texas Railroad Commission — the original page

Original format

Fixed-width Columns are byte ranges with no separators, described only in a scanned record layout.

RRC publishes

Updated twice a week (Twice a week.)

RRC download link

GoAnywhere MFT

Record layout manual

OGA096 — Well API Manual

EZRRC is an independent mirror of public-domain data published by the Texas Railroad Commission. It is not affiliated with or endorsed by the RRC. For any legal or regulatory purpose, verify against the official RRC release.