Interpret a UUID
Back
Your input: 71607332-3d02-8010-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:71607332-3d02-8010-87ea-5ce32bd83b97
URI: uuid:71607332-3d02-8010-87ea-5ce32bd83b97
Microsoft GUID syntax: {71607332-3D02-8010-87EA-5CE32BD83B97}
C++ struct syntax: { 0x71607332, 0x3d02, 0x8010, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.150703560479508990964377492485314198423
As OID (Microsoft): 1.2.840.113556.1.8000.2554.29024.29490.15618.32784.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.8169656383659212816.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1902146354.1023574032.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.29024.29490.15618.32784.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x716073323d0201007ea5ce32bd83b97]
Custom data block1 (32 bit): [0x71607332]
Custom data block2 (16 bit): [0x3d02]
Custom data block3 (12 bit): [0x010]
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: [0x7160] 0b0111000101100000
Milliseconds: [0x73] 451 (deviation -2ms..2ms)
Seconds: [0x32] 50
Minute of day: [0x023d] 573 (09:32)
Day of year: [0x100] 256 (Day=13, 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-13 09:32:50'451 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing