A timestamp is a number, and the number does not say what it means EPOCH
So this tries every format it knows and ranks the answers by which ones give a date that could be real. Seventeen formats, hex read both ways round.
The number
A decimal count, a hex blob with or without separators, or a version 1 UUID. Hex is tried most significant byte first and least significant byte first, because a disk image and a document give you opposite answers and remembering to reverse it is how mistakes happen.
What it could be
The other way round
An instant, and what every format would write for it. Read as UTC, because every epoch below is a UTC instant.
A whole column at once
One value per line, all read in the same format, which is the case once you know what the column is.
How it works
A timestamp in a file or log is just a number, and the number does not say what format it is. EPOCH tries every format it knows, including Unix time, Windows FILETIME, .NET ticks, GPS time and hex read both ways, and ranks the results by which give a date that could be real. It converts a whole column at once and shows local time and UTC. Nothing leaves this tab.
Doing this often? OBSCURA Umbra edits a folder of code where it is and runs JavaScript, TypeScript and Python over it in a sandbox. On its own, US$4 a month; with everything else, US$9 a month or US$79 a year. 7 days free.