A lookup in a formula wouldn’t really work as you have it laid out there (in the parlance of a spreadsheet).
The “rows” in Airtable don’t actually have a static spatial relationship to each other like a the rows in a spreadsheet do. They are made to look like they do on the grid view, but in the background, they are really more like floating records related to each other only in their belonging to the same table. You’ll notice that if you filter or sort differently, the row numbers still order in ascending fashion starting at 1 on top, down through the last record. In other words, what was “row 1” in one sort schema, is no longer “row 1” when you sort by another schema.
This happens because a grid view is really the graphical display of a search query being made against the database. If you have no filters, no sorts, and no groupings applied, it’s like asking the database, “Show me all records and all fields in this table”. But if you apply a filter, you are saying, “Show me all records in this table where this condition is true” - the first record returned (ie, “row 1”) may not be the first record returned when you asked for all records (no conditions). There is no static, spatial relationship going on there. In excel, the data in row 12, column A is always located there. If you hide rows, you see a gap in the numbers - the numbers don’t change. If you re-sort a table, you see the row numbers rearrange - the numbers don’t change. That’s what allows a lookup against a row/column in Excel to work - but this just won’t work in a relational database like Airtable, unfortunately.