PERMITS · ALL ON FILE
Baltic Royalty Corp. permits
Newest first by issue date. A window counts the day each permit first appeared in Railroad Commission daily files, which runs a few days behind. How permits work →
Wellbore
ShowingBaltic Royalty Corp.
4 FILINGS · 3 PERMITS · PAGE 1 OF 1
On the mapSave this search| Permit | Seen | Issued | Operator | County | Lease / well | Depth | API |
|---|---|---|---|---|---|---|---|
| 451261 | Aug 8, 1996 | Aug 8, 1996 | Baltic Royalty Corp. | Hardeman | Boyles #5 | 8,350 | 19731392 |
| 417503 | Oct 28, 1993 | Oct 28, 1993 | Baltic Royalty Corp. | Hardeman | Ferguson, S. M. III Trust #5 | 8,300 | 19731264 |
| 398805 | May 4, 1992 | May 4, 1992 | Baltic Royalty Corp. | Hardeman | Ferguson, S. M. III Trust #4 | 8,300 | 19731212 |
| 398805Amendment | May 4, 1992 | May 4, 1992 | Baltic Royalty Corp. | Hardeman | Ferguson, S. M. III Trust #4 | 8,300 | 19731212 |
About this data
Drilling permits from the RRC OGA049M master and the daily daf420 files, keyed on the day each permit first appeared in those files. Operator names as filed; application types per the RRC code table.
New to these records? how permits work · why the window is on first-seen
Developers: this page as JSON is GET /v1/data/permits/tx, documented in the API reference.