However, that does assume that the driver is simply incrementing this number, if it's not you may run into issues sooner. There's room to insert an additional 4 bits of the timestamp without any black magic, fits right in the field. It's only omitted as a result of the chosen implementation.

We need to find space for 10 additional bits in our UUID, we've just consumed 1 additional bit above (Multicast bit). We still have 7 most significant bits of the node field, so we can place 7 bits there. MongoDB's timestamp only has a resolution of a second, where as UUID v1 has a resolution of 100 nanoseconds. So there's actually 7 (least significant) bits free in the timestamp, so the remaining 3 bits can be placed there. Of course, the semantics are somewhat altered if you place those last 3 bits in UUID's time field, so this may not be desirable in all circumstances.

Convert 12-digit hexadecimal MAC address for VTAM / NCP definitions that connects Ethernet and Token Ring networks using MAC address converter online. However, if you want completely lossless (and therefore reversible) conversion, then this is at least one possible solution.

Convert mac address to uuid