Interprete a UUID
Back
Your input: 55f68125-5f05-8015-87e9-5ce32bd83b97
Various notations:
URN: urn:uuid:55f68125-5f05-8015-87e9-5ce32bd83b97
URI: uuid:55f68125-5f05-8015-87e9-5ce32bd83b97
Microsoft GUID syntax: {55F68125-5F05-8015-87E9-5CE32BD83B97}
C++ struct syntax: { 0x55f68125, 0x5f05, 0x8015, { 0x87, 0xe9, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.114264304060606026308918030910031936407
As OID (Microsoft): 1.2.840.113556.1.8000.2554.22006.33061.24325.32789.34793.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.6194280335002664981.9793460995456777111
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1442218277.1594195989.2280217827.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.22006.33061.24325.32789.34793.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x55f681255f0501507e95ce32bd83b97]
Custom data block1 (32 bit): [0x55f68125]
Custom data block2 (16 bit): [0x5f05]
Custom data block3 (12 bit): [0x015]
Custom data block4 (14 bit): [0x07e9]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x55f6] 0b0101010111110110
Milliseconds: [0x81] 505 (deviation -2ms..2ms)
Seconds: [0x25] 37
Minute of day: [0x055f] 1375 (22:54)
Day of year: [0x150] 336 (Day=2, Month=12)
Unused 2 bits: [0] 0b00
Year: [0x7e9] 2025
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2025-12-02 22:54:37'505 (deviation -2ms..2ms)