The string 202201212432 closely resembles YYYYMMDDHHMM format — a common timestamp in ticketing databases. Let’s test:
If the hour were 23 (11 PM), the minute 32 would be fine. But 24:32 doesn’t exist. This strongly suggests a bug in a ticket system’s export, or a scraper misinterpreted a 2 PM (14:00) as 24:00. alpha luke ticket show 202201212432 min 2021
The trailing min 2021 further confuses: if the show was in 2021, why does the timestamp say 2022? Possibilities: If the hour were 23 (11 PM), the minute 32 would be fine
Assuming you truly want to attend or recall purchasing a ticket for this, follow this recovery checklist: Assuming you truly want to attend or recall
If the string came from an email or receipt, try:
