Interpret a UUID
Back
Your input: 32e1ce37-5c02-8110-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:32e1ce37-5c02-8110-87ea-5ce32bd83b97
URI: uuid:32e1ce37-5c02-8110-87ea-5ce32bd83b97
Microsoft GUID syntax: {32E1CE37-5C02-8110-87EA-5CE32BD83B97}
C++ struct syntax: { 0x32e1ce37, 0x5c02, 0x8110, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.67633849144819068635676528881822088087
As OID (Microsoft): 1.2.840.113556.1.8000.2554.13025.52791.23554.33040.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.3666438308818485520.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.853659191.1543667984.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.13025.52791.23554.33040.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x32e1ce375c0211007ea5ce32bd83b97]
Custom data block1 (32 bit): [0x32e1ce37]
Custom data block2 (16 bit): [0x5c02]
Custom data block3 (12 bit): [0x110]
Custom data block4 (14 bit): [0x07ea]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x32e1] 0b0011001011100001
Milliseconds: [0xce] 807 (deviation -2ms..2ms)
Seconds: [0x37] 55
Minute of day: [0x025c] 604 (10:03)
Day of year: [0x101] 257 (Day=14, Month=9)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-09-14 10:03:55'807 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing