It depends.
Can the data controller or another person, with "means reasonably likely to be used," (see clause 26 of the preamble of the GDPR) use that data alone or in combination with other data to identify a natural person?
If yes, it is personal data within the meaning of the GDPR.
If no, it is not personal data within the meaning of the GDPR.
Anonymous data is not subject to the GDPR. "The principles of data protection should therefore not apply to anonymous information, namely information which does not relate to an identified or identifiable natural person or to personal data rendered anonymous in such a manner that the data subject is not or no longer identifiable. This Regulation does not therefore concern the processing of such anonymous information, including for statistical or research purposes."
Assigning an unique alphanumeric code to a thing does not necessarily make the code and/or the thing "personal data". But if you have a set of data that is or can be linked by the unique alphanumeric code (e.g. as a primary key in a set of tables) and you can use it to identify a person, then it is personal data.
Either way, to be GDPR-compliant / to mitigate risk you should make some kind of record to reflect that process of thinking and what you decided. And if the answer is Yes, it is personal data, then you should record your "lawful basis" for processing the data and how you decided that.